Closed Psycho0verload closed 1 year ago
Fixed with Merge #453
With the merge #453 the problem was solved. With the commit 4b82f75 this problem now exists again and the error as described above occurs again.
⠿ db Pulled 8.6s
⠿ 9815334b7810 Pull complete 2.7s
⠿ f85cb6fccbfd Pull complete 2.7s
⠿ b63612353671 Pull complete 2.8s
⠿ 447901201612 Pull complete 3.0s
⠿ 9b6bc806cc29 Pull complete 3.1s
⠿ 24ec1f4b3b0d Pull complete 3.1s
⠿ 207ed1eb2fd4 Pull complete 3.7s
⠿ 27cbde3edd97 Pull complete 3.7s
⠿ 0a5aa35cc154 Pull complete 6.2s
⠿ e6c92bf6471b Pull complete 6.3s
⠿ 07b80de0d1af Pull complete 6.3s
[+] Building 1.0s (5/6)
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 324B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/mysql:5 0.0s
=> [1/3] FROM docker.io/library/mysql:5 0.1s
=> ERROR [2/3] RUN apt-get update; 0.8s
------
> [2/3] RUN apt-get update;:
#0 0.314 /bin/sh: apt-get: command not found
------
failed to solve: executor failed running [/bin/sh -c apt-get update;]: exit code: 127
We had to revert that PR as it broke the entire setup.
We had to revert that PR as it broke the entire setup.
Ah okay - I see.
Is it an option to adjust only the /config/mysql/Dockerfile
and leave the docker-compose.yml untouched
@Cretection
I'm not sure to be honest what effect this could have.
I would like to open this ticket again, because as you can see from the pull request this item is still current
When you try to create the build for the MYSQL backups via docker compose build you get an error:
The error is due to the image used. The Mysql:5 uses Oraclelinux which works with yum and not with apt