Peter Nunn

So.. change data pemissions to a+rw for all directories and files and I've managed to manually start apache2 in the icinga2 container. I now get  Should I now manually...

pnunn@dockerhost:~$ docker -v Docker version 19.03.6, build 369ce74a3c on linux. Should clarify.. the above message is back to the multi machine setup using docker-compose, that's the one I'm trying to...

OK... there don't appear to be any more errors in the logs.. but apache didn't start when the container did so something is grumpy still by the looks.. I'll go...

OK, so the docker-compose system is obviously still borked... I tried manually setting up the icingaweb2 configuration, but ended up with this.  Might just dump all of this and...

OK, I've just worked out that the docker-compose up didn't create any database schema's either so I guess it didn't get through the setup process.

OK, got it... So, I think it was because there was no container name for the mysql container. I added container_name:mysql to the docker-compose file. I also created the data...

Sure.. here it is. [docker-compose.yml.txt](https://github.com/jjethwa/icinga2/files/4496191/docker-compose.yml.txt) (had to add the .txt to upload).

Sigh...

I keep updating warp hoping beyond hope that one day someone will look at this fish issue and fix it... Sadly... not to date. Is anyone alive out there?

Sadly warp doesn't care about fish users either.. oh well, back to the default terminal then I guess.