Docker-compose: services with volume "." are always empty

[Jean Honlet (jehon)]

In docker-compose, I have multiple services with "volume" mapped to "."

In the "devcontainer", this is mapped to a "volume", and it works fine.

But in other services, the "." is not handled.

How to map the "." to the volume?

It could be great to have a "variable" holding either "." or the volume name, but how to construct that?

[Jean Honlet (jehon)]

I found some stuff:

• https://stackoverflow.com/q/65343518/1954789: how to map to LOCAL_WORKSPACE_FOLDER
  But that requires a local checkout before launching the devcontainer

• https://github.com/h4l/dev-container-docker-compose-volume-or-bind
  It looks for mounted volumes inside the devcontainer, and extract the name of the volume, then it use it for other mounts. But that a bit complex.

[Christof Marti (chrmarti)]

Came here to suggest using "initializeCommand" like https://github.com/h4l/dev-container-docker-compose-volume-or-bind does. Instead of the longish shell script you could use default values as suggested in https://stackoverflow.com/a/69830544/7857763 for the bind mounts and have a short script called from "initializeCommand" that writes an .env file for the volume case. For the script to check if it is run in the volume case we don't have a flag at the moment, maybe use workspace_volume_name() from the script in https://github.com/h4l/dev-container-docker-compose-volume-or-bind to check for that.

[Jean Honlet (jehon)]

Am I a rare user of this use case? Should this not be implemented more widely?

[Christof Marti (chrmarti)]

I agree, we could try to do this automatically. Could you open a feature request at https://github.com/microsoft/vscode-remote-release/issues/new?assignees=&labels=&template=feature_request.md?

[Jean Honlet (jehon)]

Posted here microsoft/vscode-remote-release#7924 for anyone coming here...