Latest beta-8.2-fpm-nginx breaks apt

[beliven-daniele-sarnari]

Affected Docker Images

serversideup/php:beta-8.2-fpm-nginx

Docker Labels of the affected images

No response

Current Behavior

#6 [ 2/12] RUN apt update   && apt install -y   freetype*   libfreetype6-dev   libpng-dev   libjpeg-dev
#6 0.132 
#6 0.132 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
#6 0.132 
#6 0.134 Reading package lists...
#6 0.[144](pipeline url) E: List directory /var/lib/apt/lists/partial is missing. - Acquire (13: Permission denied)
#6 ERROR: process "/bin/sh -c apt update   && apt install -y   freetype*   libfreetype6-dev   libpng-dev   libjpeg-dev" did not complete successfully: exit code: 100
------
 > [ 2/12] RUN apt update   && apt install -y   freetype*   libfreetype6-dev   libpng-dev   libjpeg-dev:
0.132 
0.132 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0.132 
0.134 Reading package lists...
0.144 E: List directory /var/lib/apt/lists/partial is missing. - Acquire (13: Permission denied)
------
WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH
Dockerfile:13
--------------------
  12 |     
  13 | >>> RUN apt update \
  14 | >>>   && apt install -y \
  15 | >>>   freetype* \
  16 | >>>   libfreetype6-dev \
  17 | >>>   libpng-dev \
  18 | >>>   libjpeg-dev
  19 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c apt update   && apt install -y   freetype*   libfreetype6-dev   libpng-dev   libjpeg-dev" did not complete successfully: exit code: 100

Expected Behavior

apt was working before latest update https://hub.docker.com/layers/serversideup/php/beta-8.2-fpm-nginx/images/sha256-54d33833f49da61e9cac3f9f9176e85b53de073075ee059699c7fcb5fe0d5010?context=explore

Steps To Reproduce

Dockerfile:

FROM serversideup/php:8.2-fpm-nginx

ENV S6_CMD_WAIT_FOR_SERVICES=1
ENV AUTORUN_ENABLED false
ENV AUTORUN_LARAVEL_STORAGE_LINK true
ENV PHP_FPM_PM_CONTROL static
ENV PHP_FPM_PM_MAX_CHILDREN 8
ENV PHP_MAX_EXECUTION_TIME 180
ENV LOG_OUTPUT_LEVEL warn
ENV PHP_DISPLAY_ERRORS On
ENV PHP_DISPLAY_STARTUP_ERRORS On

RUN apt update \
  && apt install -y \
  freetype* \
  libfreetype6-dev \
  libpng-dev \
  libjpeg-dev

Run docker build

Host Operating System

Ubuntu 22.04

Docker Version

Docker version 25.0.3, build 4debf41

Anything else?

No response

[beliven-daniele-sarnari]

NVM, looked at latest changes https://github.com/serversideup/docker-php/releases/tag/v3.0.0-beta4 and found out the reason. Is it possible to version the beta releases @jaydrogers ? Thanks

[jaydrogers]

Came here to post the reason why.

Is it possible to version the beta releases @jaydrogers ? Thanks

I might do this. It would be good to have for production anyways, but I don't anticipate having breaking changes in the beta this point forward.

I recommend subscribing to repo updates though: https://serversideup.net/open-source/docker-php/docs/getting-started/upgrade-guide#subscribe-to-repository-updates

[beliven-daniele-sarnari]

Came here to post the reason why.

Is it possible to version the beta releases @jaydrogers ? Thanks

I might do this. It would be good to have for production anyways, but I don't anticipate having breaking changes in the beta this point forward.

I recommend subscribing to repo updates though: https://serversideup.net/open-source/docker-php/docs/getting-started/upgrade-guide#subscribe-to-repository-updates

We would love to have versioning of beta releases because we are using them in a project. We can't use the non beta because they are not php based images and that does not allow us to use some functions such as docker-php-ext-configure and docker-php-ext-install.

Alternatively, is it possible to tag the current beta image as stable with a specific version? Thanks

[jaydrogers]

When I move these to stable, they will lose the beta tag.

Follow this for updates on how I'll tag updates moving forward: https://github.com/serversideup/docker-php/issues/323

Sorry for the construction dust during the major overhaul from v2 → v3 😅

[beliven-daniele-sarnari]

When I move these to stable, they will lose the beta tag.

Follow this for updates on how I'll tag updates moving forward: #323

Sorry for the construction dust during the major overhaul from v2 → v3 😅

super, thank you very much