-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cont-init.d] 05-changer-uid-gid.sh: exited 267. - Will not start #1103
Comments
This is an issue with the docker container specifically it seems. WRONG PROJECT OOPS |
I know you've closed this... but I really am unsure what you're talking about here! |
That file I linked to was throwing for some reason. Exit 267 which I couldn't find any docs or references to. I got the little guy fishing on Google because I had 0 results! The fix in my case, while using such an old Raspberry Pi was to just downgrade versions. They have this disclaimer:
And even though I'm running a newer version of Raspberry Pi OS, I'm guessing that hardware isn't supporting something properly. The 2022.02.1 Docker image has been much more stable and reliable. Cheers! |
Apologies - yeah I don't think I had my reading glasses on properly earlier, I thought this issue was created in the repository for the Docker repo (I have now transferred it)
Did you try the second half of the upgrade notes in the readme, that suggests updating
|
Versions
(I cannot figure out how to get into your image with a shell. Command and entrypoint changes didn't work.)
Docker Image: 2022.04.3
Platform
Expected behavior
Image starts up without errors
Actual behavior / bug
Not starting and a continuous loop of:
Steps to reproduce
Start Docker container, watch it fail to run. Disk space is not an issue. What's exit 267?
Debug Token
(will not start)
This seems related perhaps more specifically to https://github.com/pi-hole/docker-pi-hole/blob/master/s6/debian-root/etc/cont-init.d/05-changer-uid-gid.sh
I didn't realize that docker support was an entirely different project with so much in it. That seems strange...
The text was updated successfully, but these errors were encountered: