Open briandfoy opened 3 months ago
This is the relevant bit from one of my workflows, so I think I'm pulling from this project.
matrix:
os:
- ubuntu-22.04
perl-version:
- '5.8'
- '5.10'
- '5.12'
- '5.14'
- '5.16'
- '5.18'
- '5.20'
- '5.22'
- '5.24'
- '5.26'
- '5.28'
- '5.30'
- '5.32'
- '5.34'
- '5.36'
- 'latest'
container:
image: perl:${{ matrix.perl-version }}
Just pulling locally, this seems to be a problem with the images perl:5.20 and earlier.
See also GitHub Actions doesn't like the older perl images today.
There are buster images https://github.com/Perl/docker-perl/issues/100
Hi @briandfoy, thanks for the report! Indeed I can reproduce this with a mere pull - affecting 5.8 to 5.20:
As pointed out by @skaji, older Perl images will need rebuild/remanifest - actually more an issue for https://github.com/docker-library/official-images cc @tianon, but they will need backfill input from us here to see what versions are rebuild-able (especially as some versions are on base Debian images that are long since unsupported.) Will test builds and see to this 💪
And just for further clarification, the deprecation is all about the image manifest format - here's crane manifest perl:5.14
for reference:
And compare this to crane manifest perl:5.40
(which shows we're actually publishing OCI manifests by default):
@briandfoy also as a workaround, you can currently pull perl:5.10-buster
et al as they are still available in the new manifest format:
coder@code-server-76549d6999-vlhff:~/docker-perl$ crane manifest perl:5.10-buster | jq
{
"manifests": [
{
"digest": "sha256:e150c5ad123b4c95d45c6c9496a2c5b3fb6e6649260c8cda980eb2f0387b81d8",
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"platform": {
"architecture": "amd64",
"os": "linux"
},
"size": 1797
},
{
"digest": "sha256:43bbbb59936b2b1d09417a8aa4835ed5824feccc3cb0745f6dba0a4b3ee66a83",
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"platform": {
"architecture": "arm",
"os": "linux",
"variant": "v7"
},
"size": 1797
},
{
"digest": "sha256:57b0318e5d602ec6e8cc6f4c54c78bfcdfd6131c3e2568374c63ed8b8d5c71aa",
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"platform": {
"architecture": "arm64",
"os": "linux",
"variant": "v8"
},
"size": 1797
},
{
"digest": "sha256:62760bf3d42a02d57e8f9320200893061fd88c4aa6623d8518626bb635030c0d",
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"platform": {
"architecture": "386",
"os": "linux"
},
"size": 1798
},
{
"digest": "sha256:d4009dcca31fa8ff51138f2bbf2602f0ec5b8b3cd0ee4a16cd01ac839b526683",
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"platform": {
"architecture": "ppc64le",
"os": "linux"
},
"size": 1798
},
{
"digest": "sha256:e38fa3db39918c604d53c415b10ab2e6c4629a8941130c6f822e2688a0c6a48e",
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"platform": {
"architecture": "s390x",
"os": "linux"
},
"size": 1797
}
],
"mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
"schemaVersion": 2
}
I checked and this seems like a larger issue than just Perl now - old versions from other languages in docker-library/official-images are also affected.
Also heads-up - in #165 we will stop building Debian Buster images entirely.
I just noticed the issue while using docker-perl-tester
So from I read we can use the -buster
images?
I should have reported back with my adjustments to my workflows. You can see what I did. This satisfies me for the time being since it works.
Today I started seeing this, which means that all of my Perl testing is borked (thanks for the heads up GitHub).
I think you are the source I'm pulling from, but if I'm not, do you know where I should report this?
At the end of the long lines is https://docs.docker.com/go/deprecated-image-specs/