bsdpy icon indicating copy to clipboard operation
bsdpy copied to clipboard

Dockerized deploy - macadmins/tftpd container keeps restarting with no reason given

Open ghost opened this issue 6 years ago • 0 comments

I'm trying to deploy bsdpy via the recommended docker solution.

I've followed the recommended steps found on the web in various places.

I actually had this working perfectly, but then I made some changes to the underlying OS. I just installed and configured some things, but it was several things and I don't know which could be related.

Then I came back to running the docker containers and the bsdpy container works fine, the web container works fine, but tftpd keeps Restarting.

Example:

CONTAINER ID                                                       IMAGE                     COMMAND                                 CREATED             STATUS                           PORTS                         NAMES
0927dfc0be0c3463d4a00ae26e572cabe1247d86ddfc10434b1b29a0094a6dc5   macadmins/tftpd           "/bin/sh -c /usr/local/sbin/start.sh"   4 hours ago         Restarting (71) 38 seconds ago                                 tftpd
20278564b3a55383e06a08cd4d55bafb1c9d30db92df9a346c713fa64ee46027   bruienne/bsdpy:1.0        "/bin/sh -c /start.sh"                  5 hours ago         Up 5 hours                       0.0.0.0:67->67/udp            bsdpy
c7db07096ffd4af1ba339f07ba25d8c9366aeb1d357bd219f32460af9d1018b8   macadmins/netboot-httpd   "nginx -g 'daemon off;'"                5 hours ago         Up 5 hours                       0.0.0.0:80->80/tcp, 443/tcp   web

And just to show that the docker instances are listening ok:

# netstat  -lnap | grep -E ':80 |:69 |:67 '
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      32637/docker-proxy
udp        0      0 0.0.0.0:67              0.0.0.0:*                           1969/docker-proxy

Except, TFTPd should be listening on UDP port 69

I have tried a LOT of things to debug this but I cannot find any output from the restarting container. I tried starting the container with --entrypoint=/bin/bash and then connecting to the container and running the commands it is supposed to execute. But the command -- /bin/sh -c /usr/local/sbin/start.sh -- just exits with no output. There are no logs, either, as far as I can tell.

I even ran the command contained within that script wrapper, which is just the tftpd daemon -- /usr/sbin/in.tftpd --listen --foreground --verbose --user user /nbi -- and that also exits with no output.

Any advice at all is greatly appreciated!

Thanks

ghost avatar Apr 12 '18 20:04 ghost