apache / pekko-connectors

Apache Pekko Connectors is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Apache Pekko.
https://pekko.apache.org/
Apache License 2.0
56 stars 27 forks source link

ironmq CI tests fail #697

Open pjfanning opened 2 weeks ago

pjfanning commented 2 weeks ago

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.
laglangyue commented 2 weeks ago

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

pjfanning commented 2 weeks ago

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

samueleresca commented 2 weeks ago

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:

pjfanning commented 2 weeks ago

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

Roiocam commented 2 weeks ago

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:

Roiocam commented 2 weeks ago

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:

Do you think this information will be helpful?

pjfanning commented 2 weeks ago

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.

laglangyue commented 2 weeks ago

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.

raboof commented 1 week ago

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?

pjfanning commented 1 week ago

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.