microsoft / microsoft/vscode-remote-release
Clone repository in container volume / docker compose / path to repository
@chrmarti is already working on this.
Since Mar 3, 2021.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Problem:
devcontainer anddocker-composer.ymlstarting the container has no information about the path to/workspaces/xxxxwhich is used to mount the cloned source code- See
.devcontainer/lsyncd.conf:7the directory should not be hard coded to/workspaces/xx:source="/workspaces/vscode-remote-test-1",
use case
sync the mounted /workspaces/xxxxx from the dev container to other container with lsyncd
steps to reproduce
-
Clone repository in container volume
https://github.com/aheissenberger/vscode-remote-clone-repo-docker-compose -
create a new volume every time - (currently only works with named volume
vscode-remote-test-1with target directoryvscode-remote-test-1- paths os hard coded!) -
the
.devcontainerfolder withdock-compose.ymlwill start the dev container and a sample phpapache container -
need to provide the path to the mounted volume including the random subdirectory (e.g.
/workspaces/xxxxx) to the dev container as an environment variable
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.