You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
It sometimes occurs that a container does not properly stop. When I take a look inside the container at the running processes, I can see that there is a "sleep 1" which comes from the script /tmp/init.sh.
`#!/usr/bin/env sh
set -uxe
export CONFIG="/tmp/config.sh"
while [ ! -f "$CONFIG" ]; do
echo "No config, sleeping for 1 second"
sleep 1
done
echo "Found config file"
`
The configuration file is apparently not created in /tmp and the container is indeed stopped after creating a config.sh file in /tmp. Do you have any idea how it can occur?
Linux distrib: Linux version 4.4.0-34-generic (buildd@lgw01-20) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
Docker version 18.06.1-ce, build e68fc7a
Thanks
The text was updated successfully, but these errors were encountered:
Hi,
It sometimes occurs that a container does not properly stop. When I take a look inside the container at the running processes, I can see that there is a "sleep 1" which comes from the script /tmp/init.sh.
`#!/usr/bin/env sh
set -uxe
export CONFIG="/tmp/config.sh"
while [ ! -f "$CONFIG" ]; do
echo "No config, sleeping for 1 second"
sleep 1
done
echo "Found config file"
`
The configuration file is apparently not created in /tmp and the container is indeed stopped after creating a config.sh file in /tmp. Do you have any idea how it can occur?
Linux distrib: Linux version 4.4.0-34-generic (buildd@lgw01-20) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
Docker version 18.06.1-ce, build e68fc7a
Thanks
The text was updated successfully, but these errors were encountered: