ironmq CI tests fail
In all recent PR builds. - eg https://github.com/apache/pekko-connectors/actions/runs/9486627304
Creating network "pekko-connectors_default" with the default driver
Creating volume "pekko-connectors_kudu-tserver-data" with default driver
Pulling ironauth (iron/auth:)...
latest: Pulling from iron/auth
[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/iron/auth:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/
Error: Process completed with exit code 1.
refference to
https://github.com/etcd-io/etcd/discussions/17811
maybe we shoulde add a version for iron/auth and iron/mq
https://hub.docker.com/r/iron/mq is unmaintained. No images have been published in years.
https://hub.docker.com/r/iron/mq is unmaintained. No images have been published in years. Yes. I think the error won't go away unless there is an image compliant with OCI standard / Docker v2.
We either:
- Don't test on iron/mq
- Republish a ironmq image that is compliant with OCI standard.
- Reach out the ironmq team
I emailed IronMQ support earlier. I'll see if they respond.
refference to etcd-io/etcd#17811 maybe we shoulde add a version for iron/auth and iron/mq
I think that's not quiet the same thing:
- the refference issue is because etcd team didn't use v2 format to publish their latest tag.
- this issue is because the docker image is not even maintained in docker hub...
I emaile IronMQ support earlier. I'll see if they respond.
Thanks.
In addition, i think ironmq team required users to build the docker image from themself, see:
- https://github.com/iron-io/dockerworker
- https://github.com/iron-io/dockers?tab=readme-ov-file
Do you think this information will be helpful?
The code in https://github.com/iron-io/dockerworker is 8/9 years old. Has checked in jars. We really have to ask ourselves, who would be using this sort of unmaintained stuff and whether Pekko should support it.
I git pull and git tag the image, the manifest will changed to schema-v2.
We have some ways to solve it:
- drop this module
- git pull, git tag, git push to pekko in dockerhub, This may involve some license issues
- Waiting for iron to fix it, but I don't think they will because the Dockerhub image has not been maintained for a long time so should we
- just disable the test
I aggre to drop the module.
I agree dropping the module seems reasonable. If someone steps up and offers to revive/maintain the module they can do so outside of the ASF.
Might be worth highlighting on the dev list?
IronMQ support suggested trying this env variable. DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE=true
This does not help on my Mac laptop. I found the setting in Docker docs but Googling it doesn't return many matches. Even if it worked, it only buys us a bit of time until Docker drops support for the old image format altogether.
