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

Use buildx tooling instead of docker API #3723

Open
devinrsmith opened this issue Apr 24, 2023 · 0 comments
Open

Use buildx tooling instead of docker API #3723

devinrsmith opened this issue Apr 24, 2023 · 0 comments
Assignees
Labels
Milestone

Comments

@devinrsmith
Copy link
Member

Historically, we've produced a set of "base" images for deephaven-core to consume as part of the build / integration testing process:

https://github.com/deephaven/deephaven-base-images
https://github.com/deephaven/deephaven-server-docker

The benefit is that developers don't need to worry about building these images themselves; there was a lot of gradle + docker cache issues that caused developer pains without the pre-built base images. Additionally, we weren't able to use this infrastructure to build production docker images since the docker API at this level does not support multi-architecture images.

Given that deephaven-core isn't responsible for our producing our docker images anymore, we may be able to go back to building these images ourselves if we can solve the caching issues.

One way to solve this might be to use more direct / modern docker tooling (buildx) as part of the build instead of using the more limited docker API; this would match the tooling we use for production images.

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

No branches or pull requests

1 participant