You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...
=> [ 9/13] RUN printf "deb-src https://packages.nginx.org/unit/debian/ ` 0.6s
=> ERROR [10/13] RUN apt-get update && apt-get install -y unit php7.0 un 1.7s
------
> [10/13] RUN apt-get update && apt-get install -y unit php7.0 unit-php:
#0 0.605 Hit:1 http://deb.debian.org/debian bullseye InRelease
#0 0.605 Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease
#0 0.605 Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
#0 0.782 Get:4 https://packages.nginx.org/unit/debian bullseye InRelease [2815 B]
#0 1.137 Err:4 https://packages.nginx.org/unit/debian bullseye InRelease
#0 1.137 The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ABF5BD827BD9BF62
#0 1.143 Reading package lists...
#0 1.701 W: GPG error: https://packages.nginx.org/unit/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ABF5BD827BD9BF62
#0 1.701 E: The repository 'https://packages.nginx.org/unit/debian bullseye InRelease' is not signed.
------
failed to solve: executor failed running [/bin/sh -c apt-get update && apt-get install -y unit php7.0 unit-php]: exit code: 100
When pulling master and running the docker-compose up -d command the build tries to pull a repository that does not have the correct key.
this can be fixed by adding the key
When pulling master and running the
docker-compose up -d
command the build tries to pull a repository that does not have the correct key.this can be fixed by adding the key
and modifying the print statements to
The text was updated successfully, but these errors were encountered: