This message was deleted.
# supports
Slackbot
11/24/2023, 2:30 PMThis message was deleted.
o
Ola Ahlman
12/08/2023, 10:49 AMAny idea for how to solve this?
s
Srikanth Chekuri
12/08/2023, 12:52 PMWhat are the logs from the exited containers?
o
Ola Ahlman
12/08/2023, 1:36 PMwhere can I find those?
s
Srikanth Chekuri
12/08/2023, 1:40 PMContainer logs
o
Ola Ahlman
12/08/2023, 3:03 PMAny specific container I should check logs for?
Ola Ahlman
12/08/2023, 3:05 PMTaking alertmanager as an example, it only has a single log from computer restart.
Copy code
level=info ts=2023-12-08T14:59:11.870Z caller=main.go:626 msg="Received SIGTERM, exiting gracefully..."Ola Ahlman
12/08/2023, 3:05 PMIts like its not configured to auto start all containers.
s
Srikanth Chekuri
12/08/2023, 3:13 PMYes, the auto restart is not enabled
o
Ola Ahlman
12/08/2023, 3:19 PMI found out that all containers was configued as restart on-failure. This seem to cause them not to correctly start on reboot.
Running this command to change all to unless-stopped seems to have solved my issue:
Copy code
docker update --restart unless-stopped $(docker ps --all -q)91 Views