[bitnami/apache] - latest (>=2.4.62-debian-12-r4) has some permission issue
Name and Version
bitnami/apache:2.4.62-debian-12-r4
What architecture are you using?
amd64
What steps will reproduce the bug?
when container on version 2.4.62-debian-12-r4 starts, it fails with permission error
apache-2.4.62-debian-12-r4
apache 14:40:19.13 INFO ==>
apache 14:40:19.14 INFO ==> Welcome to the Bitnami apache container
apache 14:40:19.14 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
apache 14:40:19.15 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
apache 14:40:19.15 INFO ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
apache 14:40:19.16 INFO ==>
apache 14:40:19.17 INFO ==> Starting Apache setup
apache 14:40:19.23 INFO ==> Generating sample certificates
Certificate request self-signature ok
subject=CN = example.com
apache 14:40:22.86 INFO ==> Found mounted virtual hosts in '/vhosts'. Copying them to '/opt/bitnami/apache/conf/vhosts'
apache 14:40:22.89 INFO ==> Mounting application files from '/app'
rm: cannot remove '/opt/bitnami/apache/htdocs': Permission denied
previous 2.4.62-debian-12-r3 works fine
apache 14:34:40.90 INFO ==>
apache 14:34:40.91 INFO ==> Welcome to the Bitnami apache container
apache 14:34:40.91 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
apache 14:34:40.92 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
apache 14:34:40.93 INFO ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
apache 14:34:40.94 INFO ==>
apache 14:34:40.95 INFO ==> Starting Apache setup
apache 14:34:41.01 INFO ==> Generating sample certificates
Certificate request self-signature ok
subject=CN = example.com
apache 14:34:42.30 INFO ==> Found mounted virtual hosts in '/vhosts'. Copying them to '/opt/bitnami/apache/conf/vhosts'
apache 14:34:42.36 INFO ==> Mounting application files from '/app'
realpath: /bitnami/apache/conf: No such file or directory
apache 14:34:42.38 INFO ==> Configuring Apache ServerTokens directive
apache 14:34:42.40 INFO ==> Apache setup finished!
apache 14:34:42.44 INFO ==> Starting Apache
[Mon Aug 26 14:34:42.491448 2024] [mpm_prefork:notice] [pid 1:tid 1] AH00163: Apache/2.4.62 (Unix) OpenSSL/3.0.13 configured -- resuming normal operations
[Mon Aug 26 14:34:42.491607 2024] [core:notice] [pid 1:tid 1] AH00094: Command line: '/opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf -D FOREGROU
so something happened between 2.4.62-debian-12-r3 and 2.4.62-debian-12-r4 which causes Permission denied error
What is the expected behavior?
container with bitnami/apache:latest tag is started without any error as with version 2.4.62-debian-12-r3
What do you see instead?
rm: cannot remove '/opt/bitnami/apache/htdocs': Permission denied
Are you able to reproduce the issue using the latest tag (2.4.62-debian-12-r5)?
I'll try latest, this is what I'm using when everything is fine. It's same as 2.4.62-debian-12-r5
Error persists for 2.4.62-debian-12-r5, latest, container doesn't start.
2.4.62-debian-12-r3 is last working.
apache 20:53:33.97 INFO ==> ** Starting Apache setup **
apache 20:53:33.99 INFO ==> Generating sample certificates
Certificate request self-signature ok
subject=CN = example.com
apache 20:53:35.07 INFO ==> Found mounted virtual hosts in '/vhosts'. Copying them to '/opt/bitnami/apache/conf/vhosts'
apache 20:53:35.08 INFO ==> Mounting application files from '/app'
rm: cannot remove '/opt/bitnami/apache/htdocs': Permission denied
We use pure upstream image, just mount vhosts configuration Try to look at it please. I'll try to reproduce it with docker commands later, but it seems as bug in upstream (bitnami).
Hi @MirKml ,
Thanks for reporting it. I have just added a fix and a new release should appear soon.
Let me know pls, when it will be released (or close a resolved). I will test latest again.
Hi @MirKml ,
Image 2.4.62-debian-12-r6 should have fixed the issues. Could you give it a try?
latest works fine
apache 10:54:06.74 INFO ==>
apache 10:54:06.74 INFO ==> Welcome to the Bitnami apache container
apache 10:54:06.74 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
apache 10:54:06.74 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
apache 10:54:06.75 INFO ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
apache 10:54:06.75 INFO ==>
apache 10:54:06.75 INFO ==> ** Starting Apache setup **
apache 10:54:06.78 INFO ==> Generating sample certificates
Certificate request self-signature ok
subject=CN = example.com
apache 10:54:08.38 INFO ==> Found mounted virtual hosts in '/vhosts'. Copying them to '/opt/bitnami/apache/conf/vhosts'
apache 10:54:08.40 INFO ==> Mounting application files from '/app'
realpath: /bitnami/apache/conf: No such file or directory
apache 10:54:08.40 INFO ==> Configuring Apache ServerTokens directive
apache 10:54:08.41 INFO ==> ** Apache setup finished! **
apache 10:54:08.43 INFO ==> ** Starting Apache **
[Tue Sep 03 10:54:08.476634 2024] [mpm_prefork:notice] [pid 1:tid 1] AH00163: Apache/2.4.62 (Unix) OpenSSL/3.0.14 configured -- resuming normal operations
[Tue Sep 03 10:54:08.476793 2024] [core:notice] [pid 1:tid 1] AH00094: Command line: '/opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf -D FOREGROUND'
You can close it as resolved, thanks.