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

Switch Docker image source from Docker Hub to GitHub Container Registry (GHCR) #68

Closed
atc0005 opened this issue Feb 4, 2022 · 0 comments · Fixed by #70
Closed

Switch Docker image source from Docker Hub to GitHub Container Registry (GHCR) #68

atc0005 opened this issue Feb 4, 2022 · 0 comments · Fixed by #70
Assignees
Milestone

Comments

@atc0005
Copy link
Owner

atc0005 commented Feb 4, 2022

As of v0.5.0 of the atc0005/go-ci project, images are available from both ghcr.io and index.docker.io.

Switch to ghcr.io to:

  • speed up CI runs
  • reduce bandwidth demands on Docker Hub
  • increase availability of images
@atc0005 atc0005 added this to the Next Release milestone Feb 4, 2022
@atc0005 atc0005 self-assigned this Feb 4, 2022
atc0005 added a commit that referenced this issue Feb 7, 2022
EXPAND LINTING TO USE UNSTABLE & OLDSTABLE CONTAINERS

Use the same matrix of containers for linting in the `Validate
Codebase` GHAW that we're already using for testing and building jobs.

This applies the minimum linting requirements in addition to testing
"unstable" linting options that may become the new baseline in the
future.

One notable difference is that out of the matrix of containers used
for linting we mark the unstable container as "experimental" and
configure the job to ignore linting errors generated by that
container. This effectively makes any linting output from the unstable
container informational only as intended.

SWITCH DOCKER IMAGE SOURCE

Switch out images from Docker Hub to Git Hub Container Registry
(GHCR).

REFERENCES

- GH-68
- GH-69
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant