pekko-connectors icon indicating copy to clipboard operation
pekko-connectors copied to clipboard

ironmq CI tests fail

Open pjfanning opened this issue 1 year ago • 10 comments

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.

pjfanning avatar Jun 16 '24 06:06 pjfanning

refference to https://github.com/etcd-io/etcd/discussions/17811 maybe we shoulde add a version for iron/auth and iron/mq image

laglangyue avatar Jun 16 '24 07:06 laglangyue

https://hub.docker.com/r/iron/mq is unmaintained. No images have been published in years.

pjfanning avatar Jun 16 '24 07:06 pjfanning

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

samueleresca avatar Jun 16 '24 07:06 samueleresca

I emailed IronMQ support earlier. I'll see if they respond.

pjfanning avatar Jun 16 '24 09:06 pjfanning

refference to etcd-io/etcd#17811 maybe we shoulde add a version for iron/auth and iron/mq image

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...

Roiocam avatar Jun 16 '24 09:06 Roiocam

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?

Roiocam avatar Jun 16 '24 09:06 Roiocam

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.

pjfanning avatar Jun 16 '24 10:06 pjfanning

I git pull and git tag the image, the manifest will changed to schema-v2.

We have some ways to solve it:

  1. drop this module
  2. git pull, git tag, git push to pekko in dockerhub, This may involve some license issues
  3. 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
  4. just disable the test

I aggre to drop the module.

laglangyue avatar Jun 17 '24 11:06 laglangyue

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?

raboof avatar Jun 17 '24 11:06 raboof

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.

pjfanning avatar Jun 17 '24 11:06 pjfanning