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
When building a DevContainer it do so in multi-stages depending on functionality. In various steps it uses some base docker image in order to finally produce the final image.
It would be nice for peoples like me that need some up today functionality if you update the image versions used for those intemidiate stages to some more recent ones. Doing so will allow the use of recent version of docker-cli, docker-cli-buildx, docker-cli-compose to be used in the process and eliminate some confusions why my docker-cli do not understand new features!
As in fact locally installed docker version does not participate in all build stages.
As of now I found that one of those image is : mcr.microsoft.com/devcontainers/base:0-alpine-3.16 , alpine 3.16 was release : 2022-05-23
Manual build of the stage shows ( vsch\bootstrap-image\0.354.0\bootstrap.Dockerfile ) :
# Delete the 0-alpine-3.16 version locally
docker image rm mcr.microsoft.com/devcontainers/base:0-alpine-3.16
# Pull 0-alpine-3.19 version locally
docker pull mcr.microsoft.com/devcontainers/base:0-alpine-3.19
# Cheat :-)
docker image tag mcr.microsoft.com/devcontainers/base:0-alpine-3.19 mcr.microsoft.com/devcontainers/base:0-alpine-3.16
And then rebuild the DevContainer
Steps to Reproduce:
As my essue was with docker composeinclude fonctionnality which was added in docker compose 2.20.3 (2023-08-11)
Not sure if it matters but I'm building DevContainer from a remote cloned repository to a docker volume.
( Ctrl+Shift+P ) / Dev Containers: Clone Repository in Container Volume
When building a DevContainer it do so in multi-stages depending on functionality. In various steps it uses some base docker image in order to finally produce the final image.
It would be nice for peoples like me that need some up today functionality if you update the image versions used for those intemidiate stages to some more recent ones. Doing so will allow the use of recent version of
docker-cli, docker-cli-buildx, docker-cli-compose
to be used in the process and eliminate some confusions why my docker-cli do not understand new features!As in fact locally installed docker version does not participate in all build stages.
As of now I found that one of those image is :
mcr.microsoft.com/devcontainers/base:0-alpine-3.16
, alpine 3.16 was release : 2022-05-23Manual build of the stage shows ( vsch\bootstrap-image\0.354.0\bootstrap.Dockerfile ) :
The last alpine vertion is 3.19.0 released : 2023-12-07. The bootstrap.Dockerfile with
mcr.microsoft.com/devcontainers/base:0-alpine-3.19
showsMy work around is to juste do this:
And then rebuild the DevContainer
Steps to Reproduce:
As my essue was with docker compose
include
fonctionnality which was added in docker compose 2.20.3 (2023-08-11)Not sure if it matters but I'm building DevContainer from a remote cloned repository to a docker volume.
devcontainer.json
docker-compose.yml
VSCode Version: 1.89.1
Local OS Version: Windows 10
Remote OS Version: N/A
Remote Extension/Connection Type: DevContainer
Logs:
The text was updated successfully, but these errors were encountered: