I use a MikroTik L009UiGS (arm architecture, RouterOS 7.16.2) as a router at home. I want to run nginx proxy manager on my router to forward trafik to internal services and for https termination. After some research I got it installed but it is not able to start and no log is shown. So, I have no clue what the reason could be. Any idea about the reason or how to investigate this?
Thank you,
Stephan
What I did:
- I extracted arm image from multi-platform image since MikroTik seems not be able to process multi-platform images: Code: Select all
skopeo copy --override-arch arm --override-variant v7 --override-os linux docker://jlesage/nginx-proxy-manager:v24.12.1 docker-archive:./jlesage_nginx-proxy-manager_v24.12.1_armv7.tar - I prepared a USB stick (see attachment 'usb.png')
- I created an VETH interface and added it to my bridge: Code: Select all
/interface veth add address=172.17.0.2/24 gateway=172.17.0.1 gateway6="" name=veth1 - I tested a hello-world nginx image which could be started and I saw logs of the container in the router's logs.
- I setup NPM container according to the setup shown at https://github.com/jlesage/docker-nginx-proxy-manager which works on my local computer:
Code: Select all
/container envs add key=DISABLE_IPV6 name=npm value=true /container mounts add dst=/config name=npm src=/usb1/nginx-proxy-manager/config /container add file=usb1/nginx-proxy-manager/jlesage_nginx-proxy-manager_v24.12.1_armv7.tar dns=172.17.0.1 envlist=npm interface=veth1 logging=yes mounts=npm \ root-dir=usb1/nginx-proxy-manager/root start-on-boot=yes workdir=/tmp - The container continuous to extract the image successfully (see attachment 'logs.png')
- When I hit the "Start" action button, the status of the container's status changes to "started", a log line "veth1 detect LAN" appears and the container's status changes back to "stopped".
- Memory is Free/Total: 305 MiB/512 MiB, USB stick is 8GB nearly empty, internal storage is Free/Total 24 MiB/128 MiB.
