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
Would it be possible to make the factory also publish an OCI image endpoint? This would allow me to do something like
docker pull factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/v1.7.6/metal-amd64:latest
and maybe make some of the extensions or builds have aliases that are easier to discover (similar to nixery ) so I could also do something like
docker pull factory.talos.dev/qemu-guest-agent/intel-ucode/talos:v1.8.1
Ideally I wouldn't need to include an architecture in the path because docker should request the proper manifest for the image.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Would it be possible to make the factory also publish an OCI image endpoint? This would allow me to do something like
and maybe make some of the extensions or builds have aliases that are easier to discover (similar to nixery ) so I could also do something like
Ideally I wouldn't need to include an architecture in the path because docker should request the proper manifest for the image.
The text was updated successfully, but these errors were encountered: