docker-php-serversideup-s6-ini fails
Closed this issue · 1 comments
pha3z commented
Affected Docker Images
serversideup/php:8.2-fpm-apache
Docker Labels of the affected images
No response
Current Behavior
I have the following dockerfile:
FROM serversideup/php:8.2-fpm-apache
ENV S6_CMD_WAIT_FOR_SERVICES=1
COPY --chmod=755 ./entrypoint.d/ /etc/entrypoint.d/
RUN docker-php-serversideup-s6-init
When I execute docker build, it breaks:
ubuntu@ip-172-31-42-15:/opt/wp-cubix/git$ docker build -t wp-cubix .
[+] Building 0.4s (7/7) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 198B 0.0s
=> [internal] load metadata for docker.io/serversideup/php:8.2-fpm-apache 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 83B 0.0s
=> CACHED [1/3] FROM docker.io/serversideup/php:8.2-fpm-apache 0.0s
=> [2/3] COPY --chmod=755 ./entrypoint.d/ /etc/entrypoint.d/ 0.0s
=> ERROR [3/3] RUN docker-php-serversideup-s6-init 0.3s
------
> [3/3] RUN docker-php-serversideup-s6-init:
0.223 /bin/sh: 1: docker-php-serversideup-s6-init: not found
------
Dockerfile:7
--------------------
5 | COPY --chmod=755 ./entrypoint.d/ /etc/entrypoint.d/
6 |
7 | >>> RUN docker-php-serversideup-s6-init
8 |
--------------------
ERROR: failed to solve: process "/bin/sh -c docker-php-serversideup-s6-init" did not complete successfully: exit code: 127
Expected Behavior
I would expect the image to build successfully.
Steps To Reproduce
I just tried to build it using the custom dockerfile I demonstrated above.
Host Operating System
Ubuntu 22.04
Docker Version
ubuntu@:/opt/wp-cubix/git$ docker version
Client: Docker Engine - Community
Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:17:48 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 26.0.0
API version: 1.45 (minimum version 1.24)
Go version: go1.21.8
Git commit: 8b79278
Built: Wed Mar 20 15:17:48 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0Anything else?
No response
pha3z commented
I guess the use of s6 initialization scripts is only supported in beta-8.3.
I fixed the problem by changing to:
"FROM serversideup/php:beta-8.3-fpm-apache"
Unfortunately, that brought me a new error:
-------------------------------------
ℹ️ Container Information
-------------------------------------
Docker user: root
Docker uid: 0
Docker gid: 0
ln: failed to create symbolic link '/etc/apache2/conf-enabled/remoteip.conf': File exists
ln: failed to create symbolic link '/etc/apache2/conf-enabled/security.conf': File exists
ln: failed to create symbolic link '/etc/apache2/conf-enabled/serversideup.conf': File exists
ℹ️ NOTICE (init-webserver-config): Enabling Apache site with SSL "off"...
ln: failed to create symbolic link '/etc/apache2/sites-enabled/ssl-off.conf': File exists
s6-rc: warning: unable to start service 10-init-webserver-config: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
I'm closing this. I'll have to investigate the new error and determine if its something I need to start a new thread for.