chainguard-dev / chainguard-dev/apko
apko build - the change to append architecture to user-specified tag name should be documented
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.7k
- Forks
- 228
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 62
Description
https://github.com/chainguard-dev/apko/pull/532
Docker can't handle multi arch images properly right now:
https://github.com/docker/buildx/issues/59#issuecomment-1073938648
Support for apko build for multi arch works around this Docker limitation by appending architecture to the user-specific tag name. This may create problems for users who follow a (1) apko build, (2) docker load, (3) docker run workflow and who have automation that expects images to have specific tag verbiage.
(That's the workflow outlined on the edu site):
https://edu.chainguard.dev/open-source/melange/tutorials/getting-started-with-melange/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the apko build documentation and the linked Chainguard education tutorial. Document that multi-architecture builds append the architecture to the user-specified tag, explain the effect on the apko build, docker load, docker run workflow, and make the expected tag naming clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100