Error: No such image: julia:1.0
cossio opened this issue · comments
I'm getting the following error on Gitlab's CI:
Using Docker executor with image julia:1.0 ...
Pulling docker image julia:1.0 ...
ERROR: Preparation failed: Error: No such image: julia:1.0 (executor_docker.go:175:0s)
We had to update the images for a recent gpg change which caused the build to fail
https://doi-janky.infosiftr.net/job/multiarch/job/amd64/job/julia/49/console
gpg: cannot open '/dev/tty': No such device or address
There's a PR open to push the changes and then we'll rebuild the images docker-library/official-images#5070
If you want you could pull a month old build of 1.0 instead of 1.0.2 https://github.com/docker-library/repo-info/blob/master/repos/julia/remote/1.0-stretch.md
$ docker pull julia:1.0-stretch
1.0-stretch: Pulling from library/julia
bc9ab73e5b14: Pull complete
5b55c75c692a: Pull complete
a6fe50c24ea1: Pull complete
Digest: sha256:c774e0fb44d0a7d01612de0f5c5edb595e23c094ba2563a2bd025dd90cbdc4ed
Status: Downloaded newer image for julia:1.0-stretch
Yeah the linux builds failed because of https://bugs.debian.org/913614, but the windows builds succeeded. So this is a case of docker-library/official-images#3835. It will be fixed by docker-library/official-images#5070, but it will take quite a while for the servers to get through all the builds.
To work around it use one of the simple tags listed on the Hub description that don't share a manifest with a windows image, like julia:1.0-stretch.
Note: 1.0.2-stretch will still fail since that is the build that failed because of the Debian bug.