Closed bobelev closed 9 years ago
hi @bobelev, this seems to be a s6-pause
bug, can you obtain the strace
log for s6-pause
, so that we'll have more info to ask in the supervision mailing list?
Do this:
FROM ubuntu
# s6 overlay
ADD https://github.com/just-containers/s6-overlay/releases/download/v1.14.0.4/s6-overlay-amd64.tar.gz /tmp/s6-overlay.tar.gz
RUN tar xvfz /tmp/s6-overlay.tar.gz -C /
# strace
ADD http://landley.net/aboriginal/downloads/binaries/extras/strace-x86_64 /usr/bin/strace
RUN chmod +x /usr/bin/strace
# replace 's6-pause' with 'strace s6-pause'
RUN sed -i 's/s6-pause/redirfd -w 2 \/logs\/s6-pause-strace.log strace -v s6-pause/g' /etc/s6/init/init-stage2
ENTRYPOINT [ "/init" ]
And execute using this:
docker build -t asdf .
docker run -v `pwd`/logs:/logs -ti asdf
And after that send the full strace log again, maybe with that Laurent would be able to solve your problem.
@bobelev any update on this?
@glerchundi, I rebuilt container to pass around this issue so I can't really reproduce it.
ok, reopen this issue if needed.
I often get messages like this:
I have node.js program that runs in docker container via systemd (coreos/fleet). It does some work and gracefully exits (
node-harmony exited 0
). In s6 layer there is only onecont-init.d
script and nothing else. ExecStop and ExecStopPost in systemd don't run for this units. Unit fails with failed state because.full log
s6-overlay: v1.14.0.4 docker version 1.7.1, build 2c2c52b-dirty base image: alpine:3.2 CoreOS beta: 766.3.0