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

Investigate using github.com/containers libraries in place of Crane #1157

Open
bcrochet opened this issue May 7, 2024 · 3 comments
Open
Assignees

Comments

@bcrochet
Copy link
Contributor

bcrochet commented May 7, 2024

@bcrochet bcrochet self-assigned this May 7, 2024
@acornett21
Copy link
Contributor

Why would we want to move to this? Is there an advantage? The concern I'd have about moving libs for something like this, is that each tool seems to treat ID's/sha's etc differently in their payloads, so in one tool the DockerID might be 1234 and in the other it's 54321 and they want you to use a different value as the ID, so we'd need to be mindful to not break existing compatability.

@bcrochet
Copy link
Contributor Author

bcrochet commented May 8, 2024

No doubt on compatibility. What I'm mainly concerned with is a bit of dogfooding the libraries that podman relies on.

@acornett21
Copy link
Contributor

That's what I thought, but wanted to be sure it wasn't some issue with our current deps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants