Corrupt File?

[david-61]

Corrupt File?

[jjethwa]

Hi @david-61

Thanks for reporting the issue. Do you mind trying to start the container up without the volume to see if it comes up ok? You shouldn't need to have to run any commands to get things going with the out of the box setup.

[david-61]

Hi @jjethwa, I just executed
docker run -p 80:80 -h icinga2 -t jordan/icinga2:latest
on a snapshot, it works good like my modified run command, but this file is still corrupt.
I tought I had to modify this file because I still have persistence problems on my test machine.
Maybe I have understanded your documentation wrong?
I created a user on my Debian system called Icinga and set a Password
and I entered the pass for the icinga and root user into the file called secrets_sql.env
and executed docker compose. everything works, until the restart.

After I restart my System I cant get acess to Icingaweb2, but the container starts according to Docker.
I cant understand this : /

[jjethwa]

Hi @david-61

This was just to prove that the container is working correctly and there are no corrupted files within it.

Let's go through the docker compose steps one more time.

1. Clone the repo to the target machine: git clone https://github.com/jjethwa/icinga2.git
2. cd icinga2
3. echo "MYSQL_ROOT_PASSWORD=<ROOT_PASSWORD>" > secrets_sql.env
4. (optional) echo "DEFAULT_MYSQL_PASS=<ICINGA_DATABASE_PASSWORD>" >> secrets_sql.env
5. docker-compose up

Can you verify that works and you can restart the container via docker compose?

[david-61]

Thanks for the tip, now I managed to get icingaweb2 after restart.
my fault was: I havent executed docker compose once after the restart. 🤦🏻‍♂️
Now everything is up and running
Thank you for your Help @jjethwa.

[jjethwa]

Great news 😄