[GH-ISSUE #885] init-stage2 failed. #749

Closed
opened 2026-02-26 06:34:15 +03:00 by kerem · 14 comments
Owner

Originally created by @Klay4 on GitHub (Feb 10, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/885

I have tried to install it in my raspberry pi 4 and it is working fine, but if i try to install it on my pi zero i receive this error:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01_s6-secret-init.sh: executing...
[cont-init.d] 01_s6-secret-init.sh: exited 267.

!!!!!
init-stage2 failed.
!!!!!

Originally created by @Klay4 on GitHub (Feb 10, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/885 I have tried to install it in my raspberry pi 4 and it is working fine, but if i try to install it on my pi zero i receive this error: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01_s6-secret-init.sh: executing... [cont-init.d] 01_s6-secret-init.sh: exited 267. !!!!! init-stage2 failed. !!!!!
kerem 2026-02-26 06:34:15 +03:00
Author
Owner

@stilltruckin commented on GitHub (Mar 27, 2021):

I'm getting the same exact error on a Raspberry Pi 3 B+ any updates on this issue?

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] 01_s6-secret-init.sh: executing...
[cont-init.d] 01_s6-secret-init.sh: exited 267.

!!!!!
init-stage2 failed.
!!!!!

<!-- gh-comment-id:808801565 --> @stilltruckin commented on GitHub (Mar 27, 2021): I'm getting the same exact error on a Raspberry Pi 3 B+ any updates on this issue? [s6-init] making user provided files available at /var/run/s6/etc...exited 0., [s6-init] ensuring user provided files have correct perms...exited 0., [fix-attrs.d] applying ownership & permissions fixes..., [fix-attrs.d] done., [cont-init.d] executing container initialization scripts..., [cont-init.d] 01_s6-secret-init.sh: executing... [cont-init.d] 01_s6-secret-init.sh: exited 267. !!!!! init-stage2 failed. !!!!!
Author
Owner

@Pizmovc commented on GitHub (Apr 6, 2021):

I'm getting the same error on my Raspberry Pi 2.

Preceding it is a warning from Docker:
docker[12903]: WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/arm/v6) and no specific platform was requested

<!-- gh-comment-id:814025937 --> @Pizmovc commented on GitHub (Apr 6, 2021): I'm getting the same error on my Raspberry Pi 2. Preceding it is a warning from Docker: `docker[12903]: WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/arm/v6) and no specific platform was requested`
Author
Owner

@Valiceemo commented on GitHub (Sep 14, 2021):

Also getting this error


[cont-finish.d] executing container finish scripts...

[cont-finish.d] done.

[s6-finish] waiting for services.

[s6-finish] sending all processes the TERM signal.

[s6-finish] sending all processes the KILL signal and exiting.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

[s6-init] ensuring user provided files have correct perms...exited 0.

[fix-attrs.d] applying ownership & permissions fixes...

[fix-attrs.d] done.

[cont-init.d] executing container initialization scripts...

[cont-init.d] 01_perms.sh: executing... 

[cont-init.d] 01_perms.sh: exited 267.


!!!!!

 init-stage2 failed.
<!-- gh-comment-id:919428614 --> @Valiceemo commented on GitHub (Sep 14, 2021): Also getting this error ``` [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01_perms.sh: executing... [cont-init.d] 01_perms.sh: exited 267. !!!!! init-stage2 failed. ```
Author
Owner

@drippyer commented on GitHub (Nov 11, 2021):

Messing around with an RPi2 and seem to be hitting this as well. Everything appears to be running but not working, logs were the only indication something was wrong with the container itself, not the Pi.

<!-- gh-comment-id:966677364 --> @drippyer commented on GitHub (Nov 11, 2021): Messing around with an RPi2 and seem to be hitting this as well. Everything appears to be running but not working, logs were the only indication something was wrong with the container itself, not the Pi.
Author
Owner

@chaptergy commented on GitHub (Nov 14, 2021):

Are you all on architecture armv6? You can run uname -m to see that information. Because the docker image uses armv7.

<!-- gh-comment-id:968360505 --> @chaptergy commented on GitHub (Nov 14, 2021): Are you all on architecture `armv6`? You can run `uname -m` to see that information. Because the docker image uses armv7.
Author
Owner

@drippyer commented on GitHub (Nov 14, 2021):

Are you all on architecture armv6? You can run uname -m to see that information. Because the docker image uses armv7.

I do believe that is the issue we are having, yes. The Pi 2 uses armv6 if I remember correctly, but I will have to double check when I get a chance.

<!-- gh-comment-id:968381503 --> @drippyer commented on GitHub (Nov 14, 2021): > Are you all on architecture `armv6`? You can run `uname -m` to see that information. Because the docker image uses armv7. I do believe that is the issue we are having, yes. The Pi 2 uses armv6 if I remember correctly, but I will have to double check when I get a chance.
Author
Owner

@kaybeebee commented on GitHub (Nov 21, 2021):

Checked "uname -m" on my Raspberry Pi Zero W.
Result: armv6l

But https://nginx.org/en/ reports:
Tested OS and platforms

  • Linux 2.2 — 4 / i386; Linux 2.6 — 5 / amd64; Linux 3 — 4 / armv6l, armv7l, aarch64, ppc64le;
<!-- gh-comment-id:974896889 --> @kaybeebee commented on GitHub (Nov 21, 2021): Checked "uname -m" on my Raspberry Pi Zero W. Result: armv6l But https://nginx.org/en/ reports: Tested OS and platforms - Linux 2.2 — 4 / i386; Linux 2.6 — 5 / amd64; Linux 3 — 4 / **armv6l**, armv7l, aarch64, ppc64le;
Author
Owner

@AirAlarm commented on GitHub (Mar 17, 2022):

Has anyone managed to make it work? I'm having the same error on RPi Zero WH

[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01_perms.sh: executing...
[cont-init.d] 01_perms.sh: exited 267.

!!!!!
 init-stage2 failed.
!!!!!
<!-- gh-comment-id:1071082118 --> @AirAlarm commented on GitHub (Mar 17, 2022): Has anyone managed to make it work? I'm having the same error on RPi Zero WH ``` [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01_perms.sh: executing... [cont-init.d] 01_perms.sh: exited 267. !!!!! init-stage2 failed. !!!!! ```
Author
Owner

@Cerbrus commented on GitHub (Jun 27, 2022):

I'm running into this exact same issue on a Raspberry Pi Zero W. Same exact error as @AirAlarm

<!-- gh-comment-id:1168001653 --> @Cerbrus commented on GitHub (Jun 27, 2022): I'm running into this exact same issue on a Raspberry Pi Zero W. Same exact error as @AirAlarm
Author
Owner

@ptv1p3r commented on GitHub (Jul 2, 2022):

Same here on rpi 3b arm v6

<!-- gh-comment-id:1172912846 --> @ptv1p3r commented on GitHub (Jul 2, 2022): Same here on rpi 3b arm v6
Author
Owner

@Nessiroj commented on GitHub (Jul 23, 2022):

more then a year later, issue isn't fixed

<!-- gh-comment-id:1193147002 --> @Nessiroj commented on GitHub (Jul 23, 2022): more then a year later, issue isn't fixed
Author
Owner

@Tiritibambix commented on GitHub (Jul 31, 2022):

Everything was working fine for months and after a reboot I got the exact same error.

<!-- gh-comment-id:1200381090 --> @Tiritibambix commented on GitHub (Jul 31, 2022): Everything was working fine for months and after a reboot I got the exact same error.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 19, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2005593444 --> @github-actions[bot] commented on GitHub (Mar 19, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Apr 30, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2840630372 --> @github-actions[bot] commented on GitHub (Apr 30, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#749
No description provided.