On 06/06/2016 11:35, Vasil Yordanov wrote:
> Docker, with ENTRYPOINT "/etc/s6-linux-init/init"
> #if { s6-mount -nwt tmpfs -o mode=0755 tmpfs "/run" }
You have commented this line, which means /run is not a tmpfs anymore,
but a subdirectory in your container filesystem.
If this subdirectory is persistent in your container, then the
/run/s6-rc:initial directory may not be empty; this could cause trouble.
/run is expected to be empty at boot time, so if you're not making it a
tmpfs, you should at least delete everything under /run before copying
stuff into it.
If it doesn't solve your issue, please use the "-v -f -s256" options to
strace when you're stracing s6-rc-init, post the result on a site like
pastebin, sprunge or tpaste, and post the URL here. (At least the -f option,
whichwill help see what the s6-ftrigrd process is doing.)
--
Laurent
Received on Mon Jun 06 2016 - 09:55:14 UTC