John Keech

I would recommend using the relative path approach. What is the Docker context set to for the build? From the examples you provided, it looks like the relative path might...

@mgabeler-lee-6rs thanks for pointing that out! I did some digging, and it looks like we used to have a feature in Codespaces that would symlink the repo root (`/workspaces/{repo}`) to...

@AsyncVoid do you mind opening a separate issue for the relative path error you are seeing? Relative path should work, but the path is relative to the Docker build context...

An alternative to this is to update the extensions to be local paths on disk inside the container, and then update the Dockerfile/image build to embed the exact version of...

It looks like the docs and the devcontainer schema are missing the fact that extensions can be referenced either by ID or by file path to the `.vsix`. The `install-extension`...

@OmarOmeiri can you please share which version of Docker Compose you have installed by running `docker-compose version`? It looks like Compose is generating images names with a hyphen when the...

It looks like Docker Compose made a breaking change in 2.8.0, which was subsequently reverted in 2.9.0. This sounds related. https://github.com/docker/compose/releases/tag/v2.8.0 >⚠️ Warning notice ⚠️ > >This release introduced a...

Yes! One of our goals is to refactor the universal image such that you can pick and choose subsets of functionality as devcontainer "features" to drop into your own custom...

Hi @rirl, thanks for the question! Can you provide more info about what you are trying to accomplish with the CLI and GitLab pipelines? We have some [examples](https://github.com/devcontainers/cli/blob/main/example-usage/README.md#ci-build-environment-example) in the...

I'm working on the change for Codespaces and expect it to be in our next extension release (1.10.0) in a few days. I'll reply back once it's on the marketplace.