Skip to content

[Bug]: The following signatures were invalid: KEYEXPIRED 1668891673 #29

@ijscoman1337

Description

@ijscoman1337

(Optional) Error message

http://deb.debian.org jessie-updates InRelease: The following signatures were invalid: KEYEXPIRED 1668891673

What went wrong?

#0 31.33 W: GPG error: http://archive.debian.org jessie-backports InRelease: The following signatures were invalid: KEYEXPIRED 1587841717 KEYEXPIRED 1668891673
#0 31.33 W: GPG error: http://archive.debian.org jessie-backports-sloppy InRelease: The following signatures were invalid: KEYEXPIRED 1587841717 KEYEXPIRED 1668891673
#0 31.33 W: GPG error: http://archive.debian.org jessie Release: The following signatures were invalid: KEYEXPIRED 1587841717

Expected behaviour

Container ran fine up untill the last time i used it, which must be between now and a few weeks ago. I have seen in a commit in 20 nov 2022 that you attempted a fix and considered it a fix.

How can we reproduce the bug?

Build container without extensions: All good

Build container with any extensions (emphasis on extensions: tested this and it happens with pretty much any extention)

FROM devilbox/php-fpm-5.3:0.21 AS php-build-ext
RUN apt-get -y update &&
apt-get install -y --no-install-recommends
git
libzip-dev

Host Operating System

Linux

Host Platform (amd64, arm64, other)

amd64

(Linux only) Is SELinux enabled?

I am not on Linux

Docker version

3.7

Log: docker logs

> [php-go 2/2] RUN apt-get -y update &&     apt-get install -y --no-install-recommends         git         golang     &&     mkdir -p /tmp/go &&     GOPATH=/tmp/go go get github.com/mailhog/mhsendmail:
#0 2.240 Ign http://archive.debian.org jessie InRelease
#0 2.403 Get:1 http://archive.debian.org jessie-backports InRelease [166 kB]
#0 4.175 Get:2 http://archive.debian.org jessie-backports-sloppy InRelease [54.5 kB]
#0 4.320 Get:3 http://archive.debian.org jessie Release.gpg [2420 B]
#0 4.504 Get:4 http://archive.debian.org jessie Release [148 kB]
#0 4.734 Ign http://archive.debian.org jessie-backports InRelease
#0 4.862 Get:5 http://archive.debian.org jessie-backports/main arm64 Packages [1115 kB]
#0 5.323 Ign http://archive.debian.org jessie-backports-sloppy InRelease
#0 5.328 Ign http://archive.debian.org jessie Release
#0 6.855 Get:6 http://archive.debian.org jessie-backports-sloppy/main arm64 Packages [28.7 kB]
#0 7.055 Get:7 http://archive.debian.org jessie/main arm64 Packages [8593 kB]
#0 14.50 Fetched 10.1 MB in 12s (836 kB/s)
#0 14.50 Reading package lists...
#0 16.01 W: GPG error: http://archive.debian.org jessie-backports InRelease: The following signatures were invalid: KEYEXPIRED 1587841717 KEYEXPIRED 1668891673
#0 16.01 W: GPG error: http://archive.debian.org jessie-backports-sloppy InRelease: The following signatures were invalid: KEYEXPIRED 1587841717 KEYEXPIRED 1668891673
#0 16.01 W: GPG error: http://archive.debian.org jessie Release: The following signatures were invalid: KEYEXPIRED 1587841717
#0 16.52 Reading package lists...
#0 18.02 Building dependency tree...
#0 18.09 Reading state information...
#0 18.13 Some packages could not be installed. This may mean that you have
#0 18.13 requested an impossible situation or if you are using the unstable
#0 18.13 distribution that some required packages have not yet been created
#0 18.13 or been moved out of Incoming.
#0 18.13 The following information may help to resolve the situation:
#0 18.13
#0 18.13 The following packages have unmet dependencies:
#0 18.13  golang : Depends: golang-doc (>= 2:1.3.3-1) but it is not going to be installed
#0 18.13 E: Unable to correct problems, you have held broken packages.

(Optional) Additional information

No response

Metadata

Metadata

Assignees

Labels

bugBug ReporttriageNeeds Triaging

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions