microsoft / microsoft/vscode-remote-release

Clone repository in container volume / docker compose / path to repository

Open
#4,093 3 comments 20 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Mar 3, 2021.

containers feature-request plan-review
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Problem:

  • devcontainer and docker-composer.yml starting the container has no information about the path to /workspaces/xxxx which is used to mount the cloned source code
  • See .devcontainer/lsyncd.conf:7 the 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-1 with target directory vscode-remote-test-1 - paths os hard coded!)

  • the .devcontainer folder with dock-compose.yml will 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.