devcontainer.json runArgs / upArgs for docker-compose command

[yannissgarra]

It would be nice to support runArgs parameter to call some args on docker-compose command.

For example, we could use the --env-file option on docker-compose command to specify custom .env file name where we set COMPOSE_PROJECT_NAME (it's a common use case to have a committed .env file but an ignored .env.local file that override some values).

(It might also be an envFile parameter in devcontainer.json to specify the .env file to use)

Thanks!

[vscode-triage-bot]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[sanmai-NL]

See also #4885.

[vscode-triage-bot]

This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

[Chuxel]

Moved from #6539

---

Hi!

I was working on setting up a dev-container with pre-installed packages in .venv and node_modules in the working directory¹. For that purpose it is beneficial to enable --renew-anon-volumes / -V (docs) as per Stack Overflow², as that was the (only?) solution I found to ignore the potentially present .venv and node_modules folders on the local machine, and make sure the dependencies are replaced if the base devcontainer-image has been updated³.
For reference, the relevant volumes of my docker-compose.yml looks like this (which I have confirmed shadows the local machine-folders):

services:
  app:
    volumes:
      - ..:/workspace:cached
      - /workspace/.venv/
      - /workspace/node_modules/

As I could see from the documentation⁴, runArgs is only supposed to work for build/docker-based scenarios, and not docker compose. Setting runArgs did not work:

"runArgs": ["--renew-anon-volumes"],

Which the linting also warned about. Is it possible to either allow runArgs to also apply for Docker Compose, or make an equivalent upArgs?

Footnotes

1. as suggested in https://github.com/microsoft/vscode-dev-containers/blob/main/containers/python-3/.devcontainer/base.Dockerfile#L41 ↩

2. https://stackoverflow.com/questions/29181032/add-a-volume-to-docker-but-exclude-a-sub-folder ↩

3. Some workarounds are to either have named volumes that developers would have to remove themselves every time there are dependency upgrades, or run an update to the dependencies, installing/removing the difference, both which are not too terrible workarounds. ↩

4. https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_image-or-dockerfile-specific-properties ↩

[vscode-triage-bot]

🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[crhan]

upArgs for docker-compose is really useful when several developers use dev container on the same server . Otherwise a project name collision will happen.