Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No arm platform packages on github #396

Closed
queeup opened this issue Oct 17, 2022 · 7 comments
Closed

No arm platform packages on github #396

queeup opened this issue Oct 17, 2022 · 7 comments

Comments

@queeup
Copy link

queeup commented Oct 17, 2022

There is no linux/arm/v6,linux/arm/v7,linux/arm64,linux/ppc64le platfom containers on github packages.

@troglobit
Copy link
Owner

Correct, those are on docker hub instead.

@queeup
Copy link
Author

queeup commented Oct 18, 2022

I request to put here ass well. On docker hub there is a pull limit. Sometimes it's annoying.

If you don't want to put here feel free to close this issue.

Thank you for your great work on this project.

@troglobit
Copy link
Owner

There are two separate workflows in GitHub actions for this. I have not had a need to add this myself, but someone else is free to sink a few hours into getting it working the same way also for ghcr.

@Gontier-Julien
Copy link
Contributor

I personally see no reason to have it also on GitHub, maybe we could add a second place where the docker images would be also uploaded.

https://docs.docker.com/docker-hub/download-rate-limit/#third-party-platforms

Even if i am also a very intensive Docker user i've never reached the pull limit.
Just seem a specific case for me.

The docker hub pull limit:

For anonymous users, the rate limit is set to 100 pulls per 6 hours per IP address. For authenticated users, it’s 200 pulls per 6 hour period.

@troglobit
Copy link
Owner

I'm leaning towards splitting the container.yml workflow into two:

  • one for docker hub to run only on releases, since it takes a good while to build,
  • and another for ghcr, which is very quick and good for regression testing during development cycles

This is the main reason for me to support ghcr, and I also don't want to end up paying for docker hub, which has been rumored from time to time.

@Gontier-Julien
Copy link
Contributor

I'm leaning towards splitting the container.yml workflow into two:

* one for docker hub to run only on releases, since it takes a good while to build,

* and another for ghcr, which is very quick and good for regression testing during development cycles

This is the main reason for me to support ghcr, and I also don't want to end up paying for docker hub, which has been rumored from time to time.

That could be the solution yeah, and i hope too that docker hub won't be paid only it would be a shame..

@troglobit
Copy link
Owner

Cool, I'll have a commit splitting them up in a while. With that we'll be closing this issue, full arch support will only be available via Docker Hub and GHCR will be solely for regression testing the Dockerfile (and the maintainer's primary $ARCH for reference).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants