nginx-proxy-manager init-stage2 failed.

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. !!!!!

Feb 10 '21 18:02 Klay4

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. !!!!!

Mar 27 '21 20:03 stilltruckin

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

Apr 06 '21 10:04 Pizmovc

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.

Sep 14 '21 18:09 Valiceemo

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.

Nov 11 '21 22:11 drippyer

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

Nov 14 '21 20:11 chaptergy

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.

Nov 14 '21 23:11 drippyer

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;

Nov 21 '21 21:11 kaybeebee

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.
!!!!!