We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Current the use of tags for different architecture might not be the recommended way to distribute containers for different platforms/architecture/os. See https://docs.docker.com/engine/reference/commandline/manifest/#manifest-annotate
https://docs.docker.com/registry/spec/manifest-v2-2/ https://github.com/opencontainers/image-spec/blob/main/image-index.md
If enabled the container specification in docker-compose/kubernetes config won't have to worry about specifying the right architecture tag.
The text was updated successfully, but these errors were encountered:
Hi, could you provide a PR for that?
Sorry, something went wrong.
I guess this is related to #112
I tried with the current nerdctl and the problem still persists
nerdctl
No branches or pull requests
Current the use of tags for different architecture might not be the recommended way to distribute containers for different platforms/architecture/os. See https://docs.docker.com/engine/reference/commandline/manifest/#manifest-annotate
https://docs.docker.com/registry/spec/manifest-v2-2/
https://github.com/opencontainers/image-spec/blob/main/image-index.md
If enabled the container specification in docker-compose/kubernetes config won't have to worry about specifying the right architecture tag.
The text was updated successfully, but these errors were encountered: