KEYEXPIRED (So I must be missing something)


I am trying to build sonarr locally against the v3-branch. The reason is to add a few poython packages for my connected scripts.

But, I run into a aKeyExpired error. And since I do not see a mention of this on the board, I assume that it is I that is doing something wrong.

I am using the Dockerfile from without chage, and I get the following

~/.dockerstack$ docker-compose up
Building sonarr3
[WARNING]: Empty continuation line found in:
    RUN  apt-key adv --keyserver --recv-keys FDA5DFFC &&  echo "deb develop main" > 	/etc/apt/sources.list.d/sonarr.list &&  apt-get update &&  apt-get install -y 	nzbdrone &&  apt-get clean &&  rm -rf 	/tmp/* 	/var/lib/apt/lists/* 	/var/tmp/*
[WARNING]: Empty continuation lines will become errors in a future release.
Step 1/8 : FROM lsiobase/mono
 ---> fe885e2315e0
Step 2/8 : MAINTAINER sparklyballs
 ---> Using cache
 ---> a9c184eb8b0c
Step 3/8 : ARG DEBIAN_FRONTEND="noninteractive"
 ---> Using cache
 ---> 26b19b321993
Step 4/8 : ENV XDG_CONFIG_HOME="/config/xdg"
 ---> Using cache
 ---> 89152bd1f18a
Step 5/8 : RUN  apt-key adv --keyserver --recv-keys FDA5DFFC &&  echo "deb develop main" > 	/etc/apt/sources.list.d/sonarr.list &&  apt-get update &&  apt-get install -y 	nzbdrone &&  apt-get clean &&  rm -rf 	/tmp/* 	/var/lib/apt/lists/* 	/var/tmp/*
 ---> Running in b5d403d7723b
Executing: /tmp/tmp.6m79XqrVbe/ --keyserver
gpg: requesting key FDA5DFFC from hkp server
gpg: key FDA5DFFC: public key "Totally Legit Signing Key <>" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
Get:1 xenial InRelease [5,143 B]
Get:2 xenial InRelease [247 kB]
Get:3 develop InRelease [13.3 kB]
Get:4 xenial/main amd64 Packages [49.5 kB]
Get:5 xenial-updates InRelease [109 kB]
Get:6 xenial-security InRelease [109 kB]
Get:7 xenial/main Sources [1,103 kB]
Get:8 xenial/restricted Sources [5,179 B]
Get:9 xenial/universe Sources [9,802 kB]
Get:10 xenial/multiverse Sources [215 kB]
Get:11 xenial/main amd64 Packages [1,558 kB]
Get:12 xenial/restricted amd64 Packages [14.1 kB]
Get:13 xenial/universe amd64 Packages [9,827 kB]
Get:14 xenial InRelease [3,558 B]
Get:15 xenial/multiverse amd64 Packages [176 kB]
Get:16 xenial-updates/main Sources [438 kB]
Get:17 xenial-updates/restricted Sources [2,696 B]
Get:18 xenial-updates/universe Sources [337 kB]
Get:19 xenial-updates/multiverse Sources [9,422 B]
Get:20 xenial-updates/main amd64 Packages [1,433 kB]
Ign:3 develop InRelease
Get:21 xenial-updates/restricted amd64 Packages [13.1 kB]
Get:22 develop/main amd64 Packages [127 kB]
Get:23 xenial-updates/universe amd64 Packages [1,022 kB]
Get:24 xenial-updates/multiverse amd64 Packages [19.3 kB]
Get:25 xenial-security/main Sources [203 kB]
Get:26 xenial-security/restricted Sources [2,243 B]
Get:27 xenial-security/universe Sources [146 kB]
Get:28 xenial-security/multiverse Sources [3,515 B]
Get:29 xenial-security/main amd64 Packages [1,063 kB]
Ign:14 xenial InRelease
Get:30 xenial-security/restricted amd64 Packages [12.7 kB]
Get:31 xenial-security/universe amd64 Packages [620 kB]
Get:32 xenial/main amd64 Packages [13.0 kB]
Get:33 xenial-security/multiverse amd64 Packages [6,282 B]
Fetched 28.7 MB in 2s (10.1 MB/s)
Reading package lists...
W: GPG error: develop InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EBFF6B99D9B78493
W: The repository ' develop InRelease' is not signed.
W: GPG error: xenial InRelease: The following signatures were invalid: KEYEXPIRED 1579793674  KEYEXPIRED 1579793674  KEYEXPIRED 1579793674
W: The repository ' xenial InRelease' is not signed.
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 220 not upgraded.
Need to get 4,434 kB of archives.
After this operation, 18.8 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
E: There were unauthenticated packages and -y was used without --allow-unauthenticated
ERROR: Service 'sonarr3' failed to build: The command '/bin/sh -c apt-key adv --keyserver --recv-keys FDA5DFFC &&  echo "deb develop main" > 	/etc/apt/sources.list.d/sonarr.list &&  apt-get update &&  apt-get install -y 	nzbdrone &&  apt-get clean &&  rm -rf 	/tmp/* 	/var/lib/apt/lists/* 	/var/tmp/*' returned a non-zero code: 100

Use the dockerfile from our github. The one that’s on DockerHub is legacy from when we used to use DockerHub for building our images. We can’t remove it (unless we delete and rebuild the repo but we’d lose our stats).

@j0nnymoe Yeah… How’s THAT for missing the obvious? :smiley:

Sooo, I just want to change SONARR_BRANCH to “preview” in order to build the v3 i assume?

I would just suggest pulling our own image that we push to dockerhub rather than building your own :stuck_out_tongue:

@j0nnymoe Well, yeah, but i thought build your own was the only way if I wanted some extra python packages to be available in the container? (again, I’m have a few custom scripts for Sonarr that I want to keep using when dockerising my stack)

You can customize the images via this:

@j0nnymoe Ahaaaa! Thank you!