Use latest images when using docker-compose in devcontainer

[adamlewisgucci]

Related to: #3128, when using docker-compose files to Rebuild and Reopen/Rebuild without Cache and Reopen, vscode does not download the latest image versions.

It can currently be worked around via initializeCommand as suggested in the other issue, but this gets quite verbose when using multiple compose files & makes for a maintenance pain, as I need to maintain the list of files in two places

• VSCode Version: 1.75.1
• Local OS Version: Windows 10
• Remote OS Version: Docker for windows
• Remote Extension/Connection Type: Docker

[chrmarti]

We only add --pull when we don't need a temporary image to include container features. This is to fix devcontainers/cli#60. When Docker Compose adds support for build contexts we can use that and remove this workaround.

[chrmarti]

Related: #7305 (comment)

[DavidS-ovm]

@chrmarti is there a way to bake features into an image so I can move the requested features from my devcontainer.json into a separate build process? We're deploying dev versions of our services as part of the docker-compose and not getting automatic updates on rebuild is painful enough that I would consider such a workaround.

[chrmarti]

You can use the Dev Containers CLI to do that and there is a GitHub action to simplify integration into CI.

[chrmarti]

You would add a second devcontainer.json that does not use Docker Compose, but only adds features and optionally uses a Dockerfile. You can then use the CLI or GitHub action to build an image from that second devcontainer.json which you the push to a container registry.