Skip to content

Service build steps with apt fail when using PHP 8.0 (Debian 11 image) #171

@wtflm

Description

@wtflm

So, I was trying to replicate a production site in need of updates in Lando. Matching the software versions I used the wordpress recipe with PHP version set to 8.0. Now, my Landofile has some QOL tooling which needs some packages to be present on the appserver service, so I run apt in its build_as_root step but as I do and start/rebuild, I get an

E: The repository 'https://mirror.mariadb.org/repo/10.5/debian bullseye Release' does not have a Release file.

and a

⚠ One of your v3 build steps failed

with the requested packages not found on the service container after the fact.

This seems to be because apt update failed since https://mirror.mariadb.org/repo/10.5/debian really is gone and the following apt install build steps were skipped.

I also found that I can lando ssh -u root into the container and up the mariadb version number in /etc/apt/sources.list.d/mariadb.list into 10.6 or 10.11 for example like so:

deb [signed-by=/etc/apt/keyrings/mariadb-keyring.pgp] https://mirror.mariadb.org/repo/10.6/debian bullseye main

If I then, continuing as root, manually run the apt update and apt install commands, they work as expected using the new URL. The problem obviously returns if I need to rebuild my services again when the source URL gets reset to the non-existent 10.5.

Is this something Lando can fix or should I just automate that version update in my build steps prior to running apt?

EDIT: Oh, right. This makes the 10.5 disappearance much less of a mystery: https://endoflife.date/mariadb

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions