You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if we could specify a buildx field in the devcontainer.json (similar to the current build field) to point to a docker-bake.hcl file. The Bake files is next generation of build definitions in docker, and is supperior to standard Dockerfiles: https://docs.docker.com/build/bake/reference/
I think the old build scheme with Dockerfiles are perfectly fine and covers 99% of all devcontainers. But when you start to have more complex setups and you want to reuse build configurations between multiple docker images it becomes much easier to maintain with Bake files.
So a suggestion would be that devcontainers (either building directly from a Dockerfile or using a docker-compose.yml) has 2 options:
build: what we have today
buildx: new feature that can point to a *.hcl file
If buildx is defined a docker buildx bake command in the background instead of normal docker build.
The text was updated successfully, but these errors were encountered:
It would be nice if we could specify a
buildx
field in the devcontainer.json (similar to the currentbuild
field) to point to adocker-bake.hcl
file. The Bake files is next generation of build definitions in docker, and is supperior to standard Dockerfiles: https://docs.docker.com/build/bake/reference/I think the old
build
scheme with Dockerfiles are perfectly fine and covers 99% of all devcontainers. But when you start to have more complex setups and you want to reuse build configurations between multiple docker images it becomes much easier to maintain with Bake files.So a suggestion would be that devcontainers (either building directly from a Dockerfile or using a docker-compose.yml) has 2 options:
build
: what we have todaybuildx
: new feature that can point to a *.hcl fileIf
buildx
is defined adocker buildx bake
command in the background instead of normaldocker build
.The text was updated successfully, but these errors were encountered: