-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/nginx] latest image: Read-only file system #63507
Comments
Hi! We are very sorry for the inconvenience. Thank you so much for reporting. In the helm chart we are mounting a volume in /opt/bitnami/nginx/conf. In order to not break previous installations, it would make sense to add |
bitnami#63507 Signed-off-by: Matt Busche <[email protected]>
Done. |
Thank you so much for the PR! The team will take a look |
* 63507: [bitnami/nginx] latest image: Read-only file system Signed-off-by: jgournet <[email protected]> * Apply change to 1.24 too --------- Signed-off-by: jgournet <[email protected]>
Name and Version
bitnami/nginx:1.25
What architecture are you using?
amd64
What steps will reproduce the bug?
Edit:
easiest way to replicate the issue is by doing this:
What is the expected behavior?
Same behavior as with the older image:
What do you see instead?
Additional information
Seems like in the new entrypoint file, there is this new code:
coming from
https://github.com/bitnami/containers/blob/main/bitnami/nginx/1.25/debian-12/rootfs/opt/bitnami/scripts/nginx/entrypoint.sh#L25
which breaks on read-only filesystems
=> maybe just adding a "||true" in the cp command would be enough to satisfy everybody?
The text was updated successfully, but these errors were encountered: