On boot exit 2 after that no problem #1809
Comments
|
Hi. This might be an issue with docker-gen that should have been fixed recently, but the updated docker-gen version is not used yet in nginx-proxy. I'll try to push a (supposedly) fixed container for you to try in the next days. |
|
The image |
|
How can i test it in the best way in a production environment? Just pull it and add it with this image infos to the compose file? Than run the new one while the other is stopped? If it dont work stop the new and start the original one again? |
|
Still wasn´t able to test this because of a lack in my skills. |
|
@wassereimer86 sorry I was pretty sure I answered your last question You just have to replace the nginx-proxy image you're using in your Docker Compose file with |
|
No problem, i´m happy for every help and such tools that are open source. 🙂 Sadly it didn´t fix the problem. 😕 Still the same issue. I restarted multiple times to test it. If i start it manually, it´s working. If you need any infos or want to test something - let me know! |
|
Still the same problem. Just want to let you know. Any other ideas on this issue? |
|
Hey there! Do you have any new informations on the topic? 🙂 |
|
@wassereimer86 I'm still completely unable to reproduce this issue. Could you share more informations about your setup ? What host and OS you are running Docker on, which version of Docker, the compose files you are using to run nginx-proxy, etc (I'll add to the list if something comes to my mind). |
|
I just realised your issue is caused by My request for additional information still stands. In the meantime, trying the separate containers setup (replacing the |
|
@buchdag I can´t use the separate container setup at the moment. I have too much things running and i´m not an docker expert. Please let me know if you need anything else or if i can help you with anything. General: Docker: Docker Compose File: services:
homeassistant:
container_name: homeassistant
image: ghcr.io/home-assistant/home-assistant:stable
volumes:
- xxx
- xxx
ports:
- xxx
restart: always
devices:
- /dev/ttyACM0:/dev/ttyACM0
environment:
- VIRTUAL_HOST=xxx
- LETSENCRYPT_HOST=xxx
depends_on:
- esphome
esphome:
container_name: esphome
image: esphome/esphome
devices:
- /dev/ttyUSB1:/dev/ttyUSB1
volumes:
- xxx
- xxx
ports:
- xxx
- xxx
restart: always
environment:
- NETWORK_ACCESS=internal
- ESPHOME_DASHBOARD_USE_PING=true
octoprint:
container_name: octoprint
image: octoprint/octoprint
restart: always
ports:
- xxx
devices:
- /dev/ttyUSB0:/dev/ttyUSB0
- /dev/video0:/dev/video0
- /dev/snd/controlC1:/dev/snd/controlC1
- /dev/video1:/dev/video1
- /dev/input/event8:/dev/input/event8
volumes:
- xxx
- xxx
environment:
- VIRTUAL_HOST=xxx
- LETSENCRYPT_HOST=xxx
- ENABLE_MJPG_STREAMER=true
- MJPG_STREAMER_INPUT=-r 1920x1080 -f 30
- NETWORK_ACCESS=internal
nginx-proxy:
container_name: nginx-proxy
image: nginxproxy/nginx-proxy
ports:
- 80:80
- 443:443
volumes:
- /var/run/docker.sock:/tmp/docker.sock:ro
- /etc/localtime:/etc/localtime:ro
- xxx/my_proxy.conf:/etc/nginx/conf.d/my_proxy.conf:ro
- xxx/vhost:/etc/nginx/vhost.d
- xxx/html:/usr/share/nginx/html
- xxx/certs:/etc/nginx/certs:ro
depends_on:
- homeassistant
- octoprint
- wordpress
acme-companion:
image: nginxproxy/acme-companion
restart: always
container_name: nginx-proxy-acme
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
- /etc/localtime:/etc/localtime:ro
- xxx/acme:/etc/acme.sh
- xxx/vhost:/etc/nginx/vhost.d
- xxx/html:/usr/share/nginx/html
- xxx/certs:/etc/nginx/certs:rw
environment:
- DEFAULT_EMAIL=xxx
- NGINX_PROXY_CONTAINER=nginx-proxy
depends_on:
- nginx-proxy
mariadb:
container_name: mariadb
image: mariadb
restart: always
ports:
- xxx
volumes:
- xxx
- xxx
environment:
- NETWORK_ACCESS=internal
- MYSQL_ROOT_PASSWORD=xxx
phpmyadmin:
container_name: phpmyadmin
image: phpmyadmin
restart: always
ports:
- xxx
environment:
- PMA_HOST=mariadb
- HIDE_PHP_VERSION=true
- NETWORK_ACCESS=internal
volumes:
- xxx
depends_on:
- mariadb
wordpress:
container_name: wordpress
image: wordpress
restart: always
ports:
- xxx
environment:
- VIRTUAL_HOST=xxx
- LETSENCRYPT_HOST=xxx
volumes:
- xxx
- xxx
depends_on:
- mariadb
wireguard:
container_name: wireguard
image: weejewel/wg-easy
restart: always
ports:
- xxx
- xxx
environment:
- WG_HOST=xxx
- PASSWORD=xxx
- WG_PORT=xxx
volumes:
- xxx
cap_add:
- NET_ADMIN
- SYS_MODULE
sysctls:
- net.ipv4.ip_forward=1
- net.ipv4.conf.all.src_valid_mark=1 |
|
I doubt that's the issue cause but your nginx-proxy container should not |
|
Could you get the Docker events log of an unsuccessful start / reboot with |
|
Also I just updated This image replaces |
How do i do that? The problem happens when starting the server. When restarting the container everything works after that.
That doesn't help. Still the same problem.
I think i did this because anything had problems without it. Couldn't remember. I think i got an error when the containers weren't ready when nginx proxy started. But don't quote me on that. I will test this again. |
Just boot your server normally, wait a bit before restarting the container then use the following command: docker events --since "timestamp of server boot" --until "$(date --iso-8601=seconds)"Use ISO 8601 for the format of the server boot timestamp date, eg I've looked at the forego stack dump you got, forego code and specifics about Go langage and it looks to me like your nginx-proxy container is receiving a syscall that forego isn't conceived to properly handle, which results in the program exiting with a stack dump. From Go's
The bolded sentence looks awfully close to what's happening in your case. |
|
Sorry for the late answer - i had a lot to do. I hope this is what you are looking for. I did it twice. |
|
In the first set of events I don't see the nginx-proxy container starting at all. Same thing at the beginning of the second set of events, the first mention of the nginx-proxy container starting is I don't know if you're missing Aren't you missing a Have you tried removing the |
Well... I really don´t know what to say. That was the problem. Sorry for stealing your time for such a problem. I´m pretty embarrassed. I always copy the informations from the Docker Hub. Perhaps you could add it to the docker compose and usage section to prevent people from running into problems. But i want to clarify that i don't blame you for this at all! |
Don't be, everything's fine 😄
Well to be honest my take on that is that the compose file is provided as a bare bone example only. Adding a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
i hope that somebody can help me. When i reboot/start my server, all Containers start, except nginx-proxy. There i get an "Exited (2)" in the status. After i make an "docker-compose up -d" it starts und runs without any problems. The logs don´t tell my anything (at least for me as a docker beginner).
`SIGQUIT: quit
PC=0x46b9e1 m=0 sigcode=0
goroutine 34 [syscall]:`
And than a lot of goroutine´s.
log.txt
The text was updated successfully, but these errors were encountered: