truenas/charts

Nginx won't deploy after last app update

Bloodis94 opened this issue · 1 comments

Hi,
I've had Nginx proxy manager for almost a week installed, i used it to make some routing experiments and today i decided to delete and reinstall the app to start with a clean slate. After using TrueNas SCALE UI to first stop and delete it i then proceded to use the Discovery function to install it again but, once reaching the "Deploying" status it would stop there without finishing the installation. The logs are almost empty but i will place what is inside them here.

Until this moment Nginx was working without problem, and no changes has been done to the NAS. I've used all defaults for the installation, changing only the timezone to Rome.

OS Version:TrueNAS-SCALE-24.04.2
Nginx Chart Version: 1.0.33

2024-08-24 13:01:39
Startup probe failed: NOT OK
2024-08-24 13:01:07
Created container nginx-proxy-manager
2024-08-24 13:01:07
Started container nginx-proxy-manager
2024-08-24 13:01:05
Successfully pulled image "jc21/nginx-proxy-manager:2.11.3" in 46.679676326s (46.679691323s including waiting)
2024-08-24 13:00:19
Add eth0 [172.16.1.190/16] from ix-net
2024-08-24 13:00:19
Pulling image "jc21/nginx-proxy-manager:2.11.3"
2024-08-24 13:00:18
Scaled up replica set nginx-proxy-manager-688bc44f5c to 1
2024-08-24 13:00:18
Created pod: nginx-proxy-manager-688bc44f5c-vbbdn
2024-08-24 13:00:18
Successfully assigned ix-nginx-proxy-manager/nginx-proxy-manager-688bc44f5c-vbbdn to ix-truenas
2024-08-24 04:01:07.513585-07:00�[1;34m❯ �[1;36mConfiguring npm user ...�[0m
2024-08-24 04:01:07.970085-07:00useradd warning: npm's uid 568 outside of the UID_MIN 1000 and UID_MAX 60000 range.
2024-08-24 04:01:08.030405-07:00�[1;34m❯ �[1;36mConfiguring npm group ...�[0m
2024-08-24 04:01:08.068638-07:00�[1;34m❯ �[1;36mChecking paths ...�[0m
2024-08-24 04:01:08.092831-07:00�[1;34m❯ �[1;36mSetting ownership ...�[0m

Hello, please take a look here #1212 (comment)

Nginx Proxy Manager does some heavy IO operations on container layers that are not supposed to be touched.
Making docker engine create a lot of overlay layers, slowing the process by a lot.

You can use the workaround mentioned in the above link until upstream changes this behaviour.

Thanks