You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When creating a new container using this scripts will fail on updating the CT with apk at line 187 pct exec "$EPS_CT_ID" -- ash -c "apk add bash >/dev/null".
As it turns out 'pct exec' sets 2 new variables in the new CT:
SSL_CERT_DIR='/usr/lib/ssl/certs'
SSL_CERT_FILE='/usr/lib/ssl/cert.pem'
Thereby the new alpine ct does not update or complete the install as alpine certs are in /etc/ssl/cert.pem.
I see that the lxc-attach command is used when installing the app, but not under container creation.
Using lxc-attach -n "$EPS_CT_ID" -- apk add bash >/dev/null
instead of pct exec "$EPS_CT_ID" -- ash -c "apk add bash >/dev/null"
gets the script to run and start the update process.
✔ Using LXC template: alpine-3.19-default_20240207_amd64.tar.xz
✔ LXC container 201 created successfully
✔ Operating System Updated
✔ Dependencies Installed
✔ Rust v1.74.0 Installed
✔ Python v3.11 and Pip v24.0 Installed
✘ Openresty not Installed
[ERROR] on line 153 with exit code 2 while executing command pkg_update
Do not know why the script /main/apps/nginx-proxy-manager/install.sh would cause that issue though.
EDIT: This error is due to Openresty not being updated to 3.19 :)
Is your feature request related to a problem? Please describe.
When creating a new container using this scripts will fail on updating the CT with apk at line 187
pct exec "$EPS_CT_ID" -- ash -c "apk add bash >/dev/null"
.As it turns out 'pct exec' sets 2 new variables in the new CT:
Thereby the new alpine ct does not update or complete the install as alpine certs are in /etc/ssl/cert.pem.
Describe the solution you'd like
According to https://bugzilla.proxmox.com/show_bug.cgi?id=5194#c4 one could use
lxc-attach -n 134 -- apk update
instead ofpct exec 134 apk update
to bypass this "bug".Describe alternatives you've considered
Another alternative from changing the code is to wait for the upstream fix to be rolled out.
https://lists.proxmox.com/pipermail/pve-devel/2024-January/061520.html
The text was updated successfully, but these errors were encountered: