Allow use on runArgs in docker-compose interface

[Rhahkeem]

Issue Type: Feature Request

In the docs for .devcontainer.json it shows that runArgs are an option when using a Dockerfile but not when using docker-compose.

Can this option also be extended to the docker-compose interface as it would allow for an easier transition when switching between the two and a more unified interface

Extension version: 0.67.3
VS Code version: Code 1.37.1 (f06011ac164ae4dc8e753a3fe7f9549844d15e35, 2019-08-15T16:16:34.800Z)
OS version: Darwin x64 18.6.0
Remote OS version: Linux x64 4.9.184-linuxkit

[chrmarti]

Most arguments to docker run are available as options in the docker-compose.yml, but not as docker-compose CLI arguments.

[Rhahkeem]

You can use them as arguments to docker-compose run which is what the extension runs if I understand correctly

[chrmarti]

We use docker-compose up to build and start all services. docker-compose run would have to be run for each service.

[Rhahkeem]

ahh

[Rhahkeem]

Potentially docker-compose run can be used for the main service and up for the rest?

[chrmarti]

Maybe what you want can be achieved by having multiple docker-compose.yml files? You can have a main one and then add to that with additional files. devcontainer.json allows you to specify multiple compose files (main one first).

[vscodebot]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!