-
Notifications
You must be signed in to change notification settings - Fork 322
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
Allow image creation to be run via docker-compose #1037
Labels
Comments
Hey @azanar , For cmake, please see how I added and tested, #1020 (comment), and lemme know if you have any questions? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe
Indirectly. I'd like to fix #1020, which is affecting my ability to hack on a C++ project within GitPod.
Describe the behaviour you'd like
I would love to be able to fire up a workspace-images build with just a docker-compose command. Something like:
To build the
workplace-images
environment, I'd imagine something like:Describe alternatives you've considered
The alternative is to fire up image creation via the contributing instruction.
This has two limitations:
.gitpod.yml
unnecessarily complicated, akin to a sort of Greenspun'sdocker-compose.yml
. Theworkspace-full
image comes withdocker-compose
. This is not to disparage the power of.gitpod.yml
. 🙂Changes required:
docker-compose.yml
file. The Dockerfile could be modeled after.gitpod.Dockerfile
dazzle
image as a base image, since buildkit could now be pulled in as an entirely separate container.docker-compose.yml
could stand up and network the services much as they are now.dazzle
runs from a singledocker-compose
setting.Changes 1-3 are captured in a PR coming soon.
Change 4 will be captured in a
dazzle
PR also coming soon.Current roadblocks:
The registry connection logic of
dazzle
very badly wants to connect overhttps
to the registry. Since the network is just a bridge between containers, I'd rather just figure out how to makehttp
work.Possible improvements:
docker push
can reach.Additional context
Worth noting that this would also work with
podman
.The text was updated successfully, but these errors were encountered: