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

Image names with a port in the registry should be valid. #22

Closed
k9withabone opened this issue Sep 14, 2024 · 0 comments · Fixed by #26
Closed

Image names with a port in the registry should be valid. #22

k9withabone opened this issue Sep 14, 2024 · 0 comments · Fixed by #26
Labels
bug Something isn't working
Milestone

Comments

@k9withabone
Copy link
Owner

From containers/podlet#91.

Image names with a port in the registry are currently parsed with everything after the : treated as the image tag, causing the parsing to fail. For example, in ghcr.io:443/containers/podlet, 443/containers/podlet is treated the image tag. Both compose_spec::service::Image::parse() and compose_spec::service::image::Name::new() need to be fixed to allow for registry ports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant