I keep getting this "ERROR tools.terminal_tool: Docker is installed but the Docker daemon is not running /usr/bin/docker version exited with code 1)". The setup goes fine until the end of the set up.

Heya all - was just trying to install using this container, and thought I would pop in and pass on what my experience has been....

I think there is something inherently wrong with this template. I tried getting the template on three different machine, and it's weird.

For instance, look at the port mapping for 9119. Seem correct. host port / container port normal, If I switch to my br0 network to get a discrete ip, the port configuration changes from host port:container port to host port:default value. Same thing when I try to actually add the mapping for the api port.

Which is another point. the template has the var to turn on the api server, but not the port mapping? Or   API_SERVER_HOST not being thee?

I also have a question about the uid 1000 thing... Werid. After all these troubles I went ahead ant tried the template from martial., everything maps to the usual 99:100. No conflicts so far.

Nigjht and day difference. When I tried this template, and I did several times, it was grueling. error on top of error. aiohttp missing one time, the port mapping, turning on the API... Murder. The template has all these vars for telegram, and has a predefined slot for dashboard fo bid to 0.0.0.0 but no mentiof bind api.

martial. also has a matching workspace container. 5 minutes to deploy those two, and I literally spent hours fighting with this template, and I just don't know why.

the martial templates make reference to requiring a share volume to get agent and workspace to work correctly. That was how it USED to be, and why i gave up on tha template long aho..updates would kill it. The workspace crew have really cleaned things up, and it seems workspace works entirely over api and 9119, at least as far as I read, and they are working for me now.

My advice, for anyone who is struggling, is to try one of the other templates. If you have to fight to fix a container deployment, you are just asking for troible in the future when an update happens and wipes out something you thought you set.

THanks for making the template. I haven't rules out that I am somehow pulling an old copy, i dunno. There is just something not right here.. I included a screenshot of what the port map changes to when I switch to br0. This does not happen in other templates of mine.

Hope someone else finds this helpful :)

Well looks like the port thing I was wrong about. Ssome and or all of my containers so that. Weird. Still, somehow just switching templates literally fixed everything.