ArchiveTeam/warrior-dockerfile

Scheduled reboot fails due to missing shutdown binary

Opened this issue · 0 comments

Cross-posting this ticket to this bug tracker. Running a shell in the container image I can confirm there's no shutdown binary in the container image. I can also confirm the container has the following restart policy via docker container inspect:

            "RestartPolicy": {
                "Name": "on-failure",
                "MaximumRetryCount": 0
            },

Maybe the solution here is to change the other project to do something other than shutdown, however, maybe this was a regression in this image when the base Debian version was updated.