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

Switch to using docker buildx #1398

Closed
yuvipanda opened this issue Jan 22, 2025 · 4 comments
Closed

Switch to using docker buildx #1398

yuvipanda opened this issue Jan 22, 2025 · 4 comments

Comments

@yuvipanda
Copy link
Collaborator

We're using docker-py with the old build infrastructure, which hasn't really been updated in years. We should move to using buildx, which unfortunately is only available via shelling out (docker/docker-py#2230). But it allows us a lot of positive functionality (like https://docs.docker.com/build/builders/drivers/kubernetes/) that probably will help with some of the building issues we now see with the 2i2c hetzner install

@manics
Copy link
Member

manics commented Jan 22, 2025

@ryanlovett has tried buildx with repo2podman #875 (comment)

@minrk
Copy link
Member

minrk commented Jan 22, 2025

Nice! I think thanks to your work @manics on creating the Engine API, this might not be too much. We can drop docker-py altogether, which seems sadly abandoned.

@ryanlovett
Copy link
Collaborator

repo2podman has been working nicely. (thanks @manics!) BuildKit parallelizes multi-stage builds which speeds up images with large python and R stacks.

@yuvipanda
Copy link
Collaborator Author

Dupe of #875

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

4 participants