docker / dev-environments

Dev Environments

This repository contains a feedback and issue tracker for Docker Dev Environments.

Getting Docker Environments

Docker Dev Environments are free as part of Docker Desktop for Mac and Windows (download).

Introduction

Docker Dev Environments make sharing and collaborating on your code easier than ever before. With just one click, you can share your work-in-progress code with your entire team for faster, higher-quality code reviews. That means less time fixing dependencies, and more time writing new code. With your whole team's work near at hand, you’re just one click away from faster code collaboration.

If you find a problem with the software, first browse the existing issues or search from the bar at the top (s to focus) and then, if you don't find your issue, open a new issue.

If you have new feature requests/improvements then please feel free to open a new feature request here, if you have a new idea not related to Dev Environments then please add something to Dockers public roadmap See the roadmap

Contribute to our roadmap

Early Access to features

For users of Docker Desktop interested in early access to new features please join our Developer Preview Program.

Security

Please do not create a public github issue. If you discover a potential security issue in this project we ask that you notify Docker Security send your report privately to [email protected]. Please do not create a public github issue.

FAQs

Q: How do I get started with Dev Environments?

A: Please read through our docs.

Q: I have a bug on Docker Desktop not related to Dev Environments.

A: Please open an issue either on for win, for mac or on engine as appropriate.

• Docker Desktop Windows
• Docker Desktop Mac
• Docker Engine

Q: How do I use the sharing feature?

A: Sharing of Dev Environments is a team feature, check out our team plans to find out more.

License

This library is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.

If you are curious about anything else Docker related then please head over to: www.docker.com

dev-environments's Issues

SSH Key is not being used to clone which makes the clone fails

Describe the bug
I add the repo to clone (Dev Environment) using SSH as an url. When cloning it fails saying that the password is not being given. However, on my pc I have the key in my user directory and usually works without any issues.

The big point here is that the SSH Key is not being used to clone which makes the clone fails.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Docker'
2. Click on 'Dev Environments'
3. On top right, put a private git ssh repo.
4. Click on Create
5. Look at the message in the container.

Expected behavior
I expect the clone to work

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Version Docker: 20.10.7

Additional context
Add any other context about the problem here.

Creating a dev environment adds an option to the .docker/docker-compose.yaml file that it cannot support

Describe the bug
When creating a new dev environment from an existing folder that contains a simple .docker/docker-compose.yaml file, a file called devenvs-docker-compose.yaml is also created in the .docker sub-directory, but that file adds some extra options to it, one of which Docker Desktop then says it cannot support.

To Reproduce
Steps to reproduce the behavior:

1. Create a folder with some simple content that you want to host with nginx (as an example)
2. Add a .docker/docker-compose.yaml file with the following content

version: '3.7'
services:
  nginx:
    image: nginx:mainline
    volumes:
      - "./www:/usr/share/nginx/html:ro"
    ports:
      - "80:80"

3. Create a new dev environment from that folder (with the Local Folder option)
4. See the exception:

The Compose file '[...]\.docker\devenvs-docker-compose.yaml' is invalid because:
services.nginx.volumes contains unsupported option: 'create_host_path'
exit status 1

Expected behavior
This simple example should be able to run, the option create_host_path was not added intentionally, so why is this added if it is not supported by the engine?

Desktop

• OS: Windows 10
• Version: 2004 (19041.1165)

Version of Docker Desktop:

Workaround
Removing the added option create_host_path that is not supported from the devenvs-docker-compose.yaml file allows it to start after anyway.

Debugging Dev Environments Locally

Tell us about your request
I have a repository which I wish to run as a 'Dev Environment'. I have added the original docker-compose.yaml to the .docker directory, however I receive an Invalid template: error when I add this repo to Dev Environments in Docker Desktop.

Modifying the master branch on a repo to debug is dangerous and inefficient. I could potentially fork the repo, but this also seems inefficient.

How can I execute the Dev Environment locally to debug the issue?

Which service(s) is this request for?
Dev Environments.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I wish to run one of my existing docker-compose repos as a Dev Environment.

Are you currently working around the issue?
No.

Can't create dev environment with private GitHub repository

Describe the bug
I can't create dev env with private GitHub repo

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Dev Environnements'
2. Fill create field with private GitHub repo
3. Click on 'Create button'
4. See error

Expected behavior
Successful creation of dev env

Desktop (please complete the following information):

• OS: OS X
• Version 12.0 Beta (21A5248p)

Removing development environment never stops

I've destroyed some unused volumes. In these, there was "compose-dev-env-quizzical_raman_db-data" one (it was not marked as "In use").
I tried to remove "compose-dev-env-quizzical_raman" but it is always in state "Removing" days after. Last message is "Removing volume compose-dev-env-quizzical_raman_db-data"

Support for private docker registries

Tell us about your request
Provide the possibility to configure and use a private docker registry (on my case one hosted on prem) for pulling, publishing and sharing docker dev envs

Which service(s) is this request for?
Improve configurability of docker dev environments feature.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I'm working for big company with tight data protection regulations and we cannot push anything to the internet easily. In order to be able to consider using docker dev envs to support our dev workflow we would need to use an on prem registry (e.g. Artifactory).

Are you currently working around the issue?
The feature is not yet being used, so we do not hav a production ready workaround. First tests are based standard docker-compose based dev containers (from within VSCode), but not in highly integrated fashion as docker dev envs whould provide.

Add mounting folder feature

It would be great if I could mount a folder to my dev environment, such as GitKraken.
Or it even can improve vscode integration.
Look at how Jet Brains products work with WSL on windows. It's mounting the project folder and IDE can detect all changes faster because of that.

Dev Environments Not Detecting Visual Studio Code Remote Containers Extension

Describe the bug
Docker Desktop - Dev Environments can't be accessed from Docker Desktop console because it cannot detect Remote Containers installation in Visual Studio Code. Git and Visual Studio Code itself have been found by Docker Desktop. However, it can't seem to find the extension, and as a result is not moving past the tools checklist screen. I've restarted Windows, Docker Desktop, and pretty much everything else, but keep getting the same results. Clicking the install button on the Remote Container item simply opens Visual Studio Code, and when you check the installation of the extension, it's installed, as can be seen from the second screenshot below.

To Reproduce
Steps to reproduce the behavior:

1. Go to Docker Desktop
2. Click on Dev Environments

Expected behavior
Docker Desktop should detect Remote Containers Extension in Visual Studio Code so that Dev Environments can be accessed from Docker Desktop.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 - Home Edition
• Version 21H1

Additional context
Add any other context about the problem here.

Checkout recursive Submodules

Tell us about your request
I think many repositories use submodules to keep microservices organized in compose, and in the main repo of stack link references for each.

Which service(s) is this request for?
Checkout recursive submodules

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Woking of Submodules of repository

Are you currently working around the issue?
No

Additional context

ability to check out multiple repos to the dev container

Tell us about your request
A clear and concise description of what you want to happen or the change you would like to see

Which service(s) is this request for?
Let us know which product(s) you want this for?

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Are you currently working around the issue?
A clear and concise description of any alternative solutions or features you've considered or are using today.

Additional context
Add any other context or screenshots about the feature request here.

Custom entrypoint/bootstrap support for dev containers

Tell us about your request
When opening a VSCode project and creating a dev container from a working Dev Environment, the dev container doesn't seem to run through any kind of bootstrap logic and skips any custom Dockerfile entrypoints.
This makes development hard, as we can't bootstrap the dev container with certain sensitive data, such as adding an SSH key as a secret and running it through ssh-add.

Which service(s) is this request for?
Docker for Mac + Dev Environments.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Already described in the feature request, but I'm effectively trying to turn a dev container into an out-of-the-box development environment, where I can pull and push code changes whenever I want, but also without compromising security.
Now, I'm not entirely familiar with how VSCode dev/remote containers work, so I could be misunderstanding or even misconfuring something, so feel free to correct me on this!

Are you currently working around the issue?
No, haven't found a way around it.

Visual Studio Code Insiders Feature Request

Docker Dev Environments to work with Visual Studio Code Insiders - Please, thank you :)

Currently, no workaround that I am aware of.

Add support for executing commands after launching IDE

When I start a dev environments container, the container properly starts my dev server command mentioned in the dockerfile/docker-compose file. But when I then open that container in VSCode, it stops the current server and starts a VSCode server. This causes you to have to manually start up the server again.

This issue could be solved by adding the ability to execute commands after starting the container in VSCode. This could be implemented by using a configuration file that lets you specify what commands to run upon launching in the IDE. This configuration file could be the one mentioned in #41.

Unable to create sample Dev Environments

Describe the bug
Unable to create sample Dev Environments from [email protected]:dockersamples/single-dev-env.git and [email protected]:dockersamples/compose-dev-env.git Git repositories on Docker Desktop version 3.5.1 (build 66090).

To Reproduce
Steps to reproduce the behavior:

1. Add the Git URL [email protected]:dockersamples/compose-dev-env.git in the Create field
2. Click Create
3. This gives the following error
   
4. However, when you click 'Start', it displays a message indicating that the image is being pulled but creates the dev environment with only one container
   

Expected behavior
I was expecting to see the Compose Dev Environment with multiple services similar to

Desktop (please complete the following information):

• OS: iOS
• Version: 11.4

Additional context
Add any other context about the problem here.

Requirements are not detected

Describe the bug
Git, VSCode and VCode Remote Containers are installed but not detected.

I clicked on Retry, updated Git, updated VSCode, restarted Docker Desktop for Windows and restarted Windows but dependencies are still not detected.

Screenshots

Network error on starting dev environment based on my own image

Describe the bug
I create a development environment based on kevinsullivan/leanvm. When I start it, I get four bright red internal-looking error messages. Docker Deskop indicates it's pulling my image, but it never finishes and seems to have failed.

To Reproduce
Steps to reproduce the behavior:
I'm running Windows 11 insider, Ubuntu 20.04 LTS in WSL2, and VSCode. Just try to create and start a development environment based on my image.

Expected behavior
Should run and allow me to launch VSCode.

Screenshots
Here's a screenshot of the series of error messages. These messages appear on my screen for a few seconds and then blink off.

Desktop (please complete the following information):

• OS: Windows 11 Beta
• Build 22000

Version of Docker Desktop:
You can find the version by clicking on the About Docker Desktop menu

version 20.10.8, build 3967b7d

Additional context
Add any other context about the problem here.

Custom dev-environment Dockerfile

Tell us about your request
If the git repository has a file, For example Dockerfile.dev, use that to build the development environment instead of pulling a pre-made image from docker hub.

Which service(s) is this request for?
Docker Desktop Dev Environments

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
While using the pre-made images is fine, it would be nice to be able to pull the necessary requirements during container build instead of installing them later, or to build a lighter container for a lean development environment

Are you currently working around the issue?
I have looked into using a normal container do do this, but being able to have docker desktop handle the whole process from pulling code to building the container would simplify the process

Docker Dev Enviroments Does not support custom directory installs.

As the name states, if you install in a custom directory, docker will not be able to detect it.

Proxy not detected

Describe the bug
I want to use private repository. I'm using a vpn and i have configure the proxy in my .gitconfig file.
I try also to configure the proxy in docker desktop

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Dev Environments'
2. Paste private gitlab url repo (in my case) who need proxy configuration
3. Click on 'Create'
4. See error

Preparing to clone inside a volume
Installing credential helpers... done
Cloning into '/code'...
fatal: unable to access 'https://*************************/docker.git/': Could not resolve host: *************************
exit code 128

Expected behavior

• use proxy conf in ~/.gitconfig files
• clone the private repo https://*************************/docker.git
• run the docker-compose in the repo (i don't know whats append here, it's my first time with docker Dev Environments)

Desktop (please complete the following information):

PS: Sorry in advance for my english

Error invoking remote method 'dev-envs-backend' when click on "Open in VSCode"

Describe the bug
Got a red error message when I try to "open in VSCode" : Error invoking remote method 'dev-envs-backend': Error: {"Message":"Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.41/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.devenvironments.name%3Dsingle-dev-env-keen_lehmann%22%3Atrue%7D%7D&limit=0\": context canceled"}

To Reproduce
Steps to reproduce the behavior:

1. Open Docker Desktop
2. Choose "Dev Environments (Preview)"
3. Click "START" on single-dev-env line
4. Wait for container running
5. Click "OPEN IN VSCODE" button on the running container

Expected behavior

• VScode is opened with the code from the container.

Screenshots

Desktop (please complete the following information):

• Windows 10 Entreprise 21H1 (OS build 19043.1083) 64-bit
• Docker Desktop 3.5.2

Additional context
Similar to #28 but not the same error message.

Needed to restart the container to get it connected to VSCode

Describe the bug
Download either my own container from docker hub or the single-dev-env container, and on first start, the connection to VS Code fails.

To Reproduce
Steps to reproduce the behavior:

1. Pull the image
2. Wait for VS Code to run and fail.
   Errors attached in screen shots.

Expected behavior
It should run as it does when the containers are restarted and vscode manually selected.

Screenshots
Attached.

Desktop (please complete the following information):

• OS: WinBlows
• Version 10Pro, Version 10.0.19042 Build 19042

Additional context
Love the idea, hope it gets to Linux some day.

Specify branch when cloning

Tell us about your request
Add the ability to specify or select a branch when creating a new Dev Environment from a git repository.

Which service(s) is this request for?
Docker Desktop's Dev Environments.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
For most of the projects I work on, I would need to specify a branch when cloning/creating a Dev Environment from a git repo, and from what I can tell this is currently not possible with Dev Environments.

Are you currently working around the issue?
No, as I'm not aware of any workarounds.

Offline Sharing for Individuals without a Team plan

Tell us about your request
Offline Sharing for Individuals without a Team plan

Which service(s) is this request for?
Dev Environments Sharing

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I don't have a Team plan because I'm not part of any organization that pays that plan. I want to try the sharing dev environments feature but I'd have to pay for said plan. I think if you're going to paywall this feature you should provide an alternative for users that don't want to pay the Team plan.

Are you currently working around the issue?
Haven't found a way to work around the issue. I guess one way would be to create an image from the container and push it to a registry, which is the old approach and defeats the purpose of the new dev environments feature.

Additional context

Dev Environments: Error on OPEN IN VSCODE

While trying Dev Environments feature, I got a bug when I click "OPEN IN VSCODE" button, it shows an error as in screenshot.

Steps to reproduce the behavior:

1. Open Docker Desktop
2. Choose "Dev Environments (Preview)"
3. Click "Compose bases dev environment"
4. Wait for docker-compose finishes
5. Click "OPEN IN VSCODE" button on any container

Expected behavior

• VScode is opened with the code from the container.

Screenshots

System

• Windows 10 21H1 (OS build 19043.1110) 64-bit
• Docker Desktop 3.5.2
• Windows Username: lutaiphong

Provide the ability to mount the source code volume into the docker-compose service containers at custom mount points

Tell us about your request
When a git repo is cloned it is into a volume and then the .docker/docker-compose.yaml file in that volume is read and executed - but the original volume containing the source code isn't available to the docker-compose service containers. It would be great to have the ability to say, in the docker-compose.yaml file, something like "In service A mount the source code volume to this path" and "In service B mount the source code to this other path". I'm sure this would be easy using named volumes except the source code volume has a dynamic name so some sort of pre-defined alias would be needed.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
When developing using docker with the source code on the local filesystem you can use mounts to mount the source code into the docker containers but this is slow because of the file sync process needed for Mac and Windows. By using Dev Environments and directly cloning a git repo into a volume you avoid this but the source code volume still needs to be available to the docker-compose services or nothing works.

Where do I find tutorial to create development environment for Java EE

Tell us about your request
It would be nice to have a tutorial explain how to setup up JavaEE/JakartaEE dev environment on Windows host machines including setting:

1. jdk
2. maven
3. WAS/Open Liberty server container
4. ecllipse for JavaEE
5. SVN plugin for eclipse
6. Eclipse proxy setting
7. Possibly add more tools such as VSCode, DBeaver, Postman, IntelliJ Ultimate, Notepad++ etc

Which service(s) is this request for?
How to create docker image for the above

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I am trying to solve the problem to automate setting of JavaEE dev environment on developer machine that can be then used whenever needed to consistently setup the dev env in minutes on Windows host machines.

Are you currently working around the issue?
I dont have one, currently, I just have a Word document explaining how to setup the above. I find it very obsolete way of doing dev env setup. There must be a better way. VM are slower and take more space, so it is not something I have looked into.

Additional context
Add any other context or screenshots about the feature request here.

Support vscode container description .devcontainer

Tell us about your request
You use the vscode remote development feature, but you implemented your own configuration system. Why not support .devcontainer configuration? I've already added those files to some of my repositories and now I would have to change everything to your custom system.

Which service(s) is this request for?
Single container and Compose based dev environments

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
For my environments I sometimes need specific extensions or need to configure external mounts. With .devcontainer this is already possible, but not with .docker configuration.

Are you currently working around the issue?
Currently i would not using dev environments. Instead i would directly use the vs code remote container system.

Environments Are Not Deleted

I'm deleted old environment in the list.

Desktop (please complete the following information):

• OS: [Win21H1 (OS Build 22000.100]
• Version [Docker version 20.10.7, build f0df350]

Screenshots

Ability to provide ssh keys for cloning

Tell us about your request
A clear and concise description of what you want to happen or the change you would like to see

Which service(s) is this request for?
Let us know which product(s) you want this for?

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Are you currently working around the issue?
A clear and concise description of any alternative solutions or features you've considered or are using today.

Additional context
Add any other context or screenshots about the feature request here.

VSCodium support

Tell us about your request
It would be great if VSCodium was supported by Docker Dev Environments. I'm not sure if this is possible because the Remote Containers extension doesn't seem to be available on VSCodium.

Are you currently working around the issue?
I reinstalled VSCode in order to try Docker Dev Environements.

compose file in .docker dir needs to explicitly be .yaml and a .yml is not recognized

Describe the bug
yaml and yml tend to be interchangeable in most YAML implementations (like docker compose proper). However, the docker-compose.yaml in the .docker directory explicitly needs to have the a in it and yml is not recognized.

To Reproduce
Steps to reproduce the behavior:

1. Generate a docker compose setup
2. Add a docker-compose.yml file to the .docker dir
3. The environment is started with the default docker dev container

Expected behavior
The docker-compose.yml is used to setup your environment

Desktop (please complete the following information):

• OS: MacOS
• Version: 10.4

Version of Docker Desktop:
3.6.0

Remote support: respect `docker context` or $DOCKER_HOST

Tell us about your request
Docker only only starts containers locally, even if I have set a $DOCKER_HOST var.

Which service(s) is this request for?
Docker dev environments

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

I am using docker context to manage & develop off remote containers from my local machine. I love how docker dev environments makes it simple to stop/start these instances, but I cannot use my remote environment. It can also use VS Code Remote to connect to the container, as normal.

Are you currently working around the issue?
I am using traditional docker commands, not Docker Dev Environments.

Facing unknown host prompt when connecting to VPN git server on port 7999

When using a custom git server, with an internal custom host, I was unable to move past the "this is an unknown host" prompt. This is from the logs.

The authenticity of host '____ (###.###.###.###)' can't be established.
ECDSA key fingerprint is SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
Are you sure you want to continue connecting (yes/no/[fingerprint])? 

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Dev Environnements'
2. Fill create field with internal git server
3. Click on 'Create button'
4. See error

Expected behavior
New unknown hosts to be added automatically, or open a terminal or similar to allow for responding to prompts.

Desktop (please complete the following information):

• OS: Big Sur 11.4
• Version Docker Desktop 3.5.2

Failed Environment Can't be Removed

Describe the bug
I started an environment from the initial Dev Environments page and then tried to cancel/remove it while it was initializing. I didn't realize it was trying to start or I would have waited. Now that environment can't be removed.

To Reproduce
Steps to reproduce the behavior:

1. Paste a github link in the top right box, and click "Create"
2. As soon as the process starts, hit the trash icon
3. Error Thrown:
   
4. One of the times it didn't lead to the Error state, it led to the Removing state which now can't be removed from the gui.

Expected behavior
Perhaps block the trash icon until it starts or reaches a point where deleting / trashing is safe? Perhaps find a way to remove a failed environment properly.

Screenshots
Sometimes it ends up in an "error" state and those can be removed.

At least once it's led to the "removing" state which can't be removed.

Desktop (please complete the following information):

It happened on 3.5.0

No change on 3.5.1

Additional context
It seems to still be working, just looks ugly in the UI.

Great work on this new feature everyone, I'm really excited about this new potential for our team.

How to reinstall environments

If use vscode remote container extension, all config define in .devcontainer folder.
If config change vscode will waring rebuild image and reload window.

i start use Docker Development Environments by clone 1 project git. If project does not have enough environments how can i add config and rebuild Development Environments. for example i want to add mysql docker, ... etc.
If you have to have a full configuration before creating "Docker Development Environments", it's inconvenient

I have read the documentation many times but really I don't fully understand how "Docker Development Environments" works.

cant create container if there is a dot in the git url

Describe the bug
cant create container if there is a dot in the git url.
Like: http://gitlab.com/Firstname.Lastname/XXXX.git

When a new user is created in Active Directory, the Full name field is always generated in FirstName LastName format.

To Reproduce
Steps to reproduce the behavior:

1. create a user that username is mail style(Firstname.Lastname)
2. create a repo

Expected behavior
Like git clone, support all git url

Desktop (please complete the following information):

• OS: window
• Version: 10

Additional context
What is a valid email address?

VSCode is not detected

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:73CF25EE-6654-41BA-918C-DBE649F7E4B2/20210710203913

Actual behavior

In "Dev Environments", neither Visual Studio Code nor Visual Studio Code Remote Containers Extension are detected.
Visual Studio perfectly sees containers. I'm able to start a container from Visual Studio.
I've restarted Docker desktop 2 times. Uninstalled Visual Studio as user and installed as system. All without success. It is always not seend by Docker Desktop.

Expected behavior

Information

• Windows Version: W10
• Docker Desktop Version: last one
• WSL2 or Hyper-V backend? WSL2 activated
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: no, on my PC

support for alternative IDEs

Tell us about your request
A clear and concise description of what you want to happen or the change you would like to see

Which service(s) is this request for?
Let us know which product(s) you want this for?

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Are you currently working around the issue?
A clear and concise description of any alternative solutions or features you've considered or are using today.

Additional context
Add any other context or screenshots about the feature request here.

Creating a new dev environment from the dockersamples/single-dev-env repository does not recognise Go as main language

Description
When following the instructions at https://docs.docker.com/desktop/dev-environments/#start-a-single-container-dev-environment, creating a new Environment does not recognise Go as the main language of the repository and so uses docker/dev-environments-default as base image instead of docker/dev-environments-go. This means the commands make and go are not available to run in the container.

To Reproduce

1. Go to https://docs.docker.com/desktop/dev-environments/#start-a-single-container-dev-environment
2. Follow the instructions
3. When executing the step make run, see the error: command make not available

Expected behavior
The command make should be available from the docker/dev-environments-go image to run a local webserver hosting at port 80.

Desktop

• OS: Windows 10
• Version 2004 (19041.1165)

Version of Docker Desktop:

Workaround
This problem can be resolved by specifying the correct base image, like explained in https://docs.docker.com/desktop/dev-environments/#specify-a-base-image. But as mentioned there, this is not a lasting fix and moreover the docs specify that the langauge should be recognised automatically and I can imagine not everyone will find this workaround.

Provide More Clarity on the Difference with dev-environments and VSCode Remote Containers

I'm excited to see where this goes, as devcontainers is absolutely a killer feature, but I've not been able to fully spread adoption as half the team uses Goland and the others VSCode.
I think a docker compose file is a great solution to be the source of truth that works in a variety of situations.

I'd ask if possible that the docs or readme be updated to be specific about where this is different essentially than the devcontainers feature as this was my first question and I couldn't easily figure that out.
I'd guess that many of the early tests are familiar with devcontainers and having it be addressed to show where they work together and where they are separate would be useful.

The devcontainer configuration per repo I feel is actually counterproductive compared to a shared repo with all tools standardized so I'd prefer the format I see with Docker Devcontainers personally. I think it would reduce the maintaince effort overall. By this I mean, a Go dev environment can have standard tooling, but it doesn't really need to change much on a per repo level basis.

Yes you can do this with Devcontainers in some ways, but it's designed initially for a per project approach.

Look forward to further updates.

note: Suggest that using the github discussions feature instead of issues might lead to a little better feedback/qa for the early access users. I've seen this used to good effect with the codespaces beta.

UI disappears when "Dev Environments" is selected

Describe the bug
The normal screen comes out for a while, and then all UI disappears.
Occurs only when you click the "Dev Environments" menu.

To Reproduce
Steps to reproduce the behavior:

1. Dashboard open
2. Click on 'Dev Environments'
3. See error

Expected behavior

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: macOS
• Version 11.4

Additional context
Add any other context about the problem here.

Support for a devenvironment.yaml configuration file

Currently, the Dev Environments feature automatically looks for the docker-compose file located at ".docker/docker-compose.yaml" in the root directory. The following are some of the downsides of doing this.

• It bypasses any additional configurations that can be made
• It prevents you from specifying a path to the container configuration file
• It requires you to create a new docker-compose.yaml file, if you want one located in the root directory

To fix these problems, it should look for a devevironment file located at either ".docker/devenvironment.yaml" or ".devenvironment.yaml" in the root directory. You should only look for a docker-compose file if a devenvironment file is not located. By implementing this solution, not only will the problems above be fixed, but you could also implement additional features easier.

Windows Git always need to install

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:
1.

2.

3. wsl docker-compose can't shut down

i want to konw how can i solve these problems，thanks！

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10
• Version: Docker version 20.10.7, build f0df350

Additional context
Add any other context about the problem here.

Error when launching sample dev environment: "No such image"

Describe the bug
When trying to launch the example "single container dev environment", I receive this error:

Error invoking remote method 'dev-envs-backend': Error: {"Message":"Error response from daemon: No such image: docker/dev-environments-go:stable-1"}

To Reproduce
Steps to reproduce the behavior:

1. Go to Dev Environments [Preview] for the first time
2. Click on "Single container dev environment" under "Try running a sample"
3. Wait for about 30 seconds for the dev environment container to finish trying to launch itself
4. See error

Expected behavior
I expected not to receive an error, and to be able to use the sample dev environment (I don't know what that would look like exactly, as I haven't used this feature before).

Screenshots

Logs as shown if I click on the row: (doesn't contain anything meaningful)

Desktop (please complete the following information):

• OS: macOS 11.4, on an M1 macbook air
• Docker Version 3.5.1 (3.5.1.7)

Additional context

After upgrading to Docker Version 3.5.2 (3.5.2.18), I get the same error but in the logs instead of as a banner:

Error response from daemon: No such image: docker/dev-environments-go:stable-1

I still get the same error if I delete the dev environment and try again.

I also get a different error if I try to use the other sample environment from the "Compose based dev environment" button:

Docker Desktop Dev Environment & Git Stuck State with no way to interact with the process to approve...

Describe the bug
Initialized a dev environment create request using gitHub SSH pathway. It's stuck in QA state with the following log:

**"RSA key fingerprint is SHA256:##############################

To Reproduce
Steps to reproduce the behavior:

1. Open Docker Desktop (For Mac)
2. Click on 'Dev Environments'
3. Click on textfield in the upper right hand corner and enter in private git ssh path
4. Click on the 'Create' button
5. After a short time, click on the environment record, read the log it's stuck in terminal Q/A of

Expected behavior
Expected a clear and complete outcome of a git repo to run an environment.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OSX, Big Sur
• Version 11.4

Additional context

Can't create dev environment with non-GitHub server

Describe the bug
I'm unable to clone from an internal/private/on-prem git repo - accessed through a corp VPN - and the error logged seems to hint at something related to the DNS resolver.

"Logs" extract:

Cloning into '/code'...
fatal: unable to access 'https://corp.repo.internal/my/project/': Could not resolve host: corp.repo.internal

(gh clone and git clone against that server works fine on my machine normally)

Write
To Reproduce
Steps to reproduce the behavior:

1. Paste the URL of a server which is not resolvable on the internet (e.g. corp.repo.internal)
2. Click on 'Create'
3. See container not starting, Logs for error

Expected behavior
Since the server name can be resolved on the host (-when connected through VPN), it should also work from inside Docker Engine / the UI.

Desktop (please complete the following information):

• macOS Big Sur (11.4)
• Docker 3.5.2.18

[WSL2] can't open vs-code with button to open the sample container

Describe the bug
I can not open vs-code with button to open the container

To Reproduce
I am using Docker for windows with the WSL2 integration .
I start the single container sample and press the button after its started

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• Windows 10 pro
• 19043.1110

Additional context
Docker engine 19043.1110
WSL2 integration enabled

Opening a service container in vscode stops the container's original running service

Describe the bug
When creating a dev environment from a repo that has a .docker/docker-compose.yaml definition and then selecting one of the running services to access and work on within VSCode, the service is restarted with the command /sbin/docker-init -- sleep infinity`. Doing this replaces the original running functionality of the container. When wanting to edit source code and then access it via, say, a running apache or php-fpm service everything basically breaks.

To Reproduce
Steps to reproduce the behavior:

1. clone a repo with a .docker/docker-compose.yaml file containing 1 or more services that have running services (e.g. apache or php-fpm).
2. select to access one of the services with vscode

Expected behavior
I'd expect to have access to the container with the original service still running. I can understand if the container needs re-starting to mount the additional volumes but when doing so the original start command should be preserved.

** Possible workaround **
If the ability to mount the source code into service containers suggested in feature #51 was available then a special extra service could be defined within the docker-compose.yaml file specifically for source code editing. Alternatively, Docker Dev Environments could offer the option to create an additional service container for you. But both of these require feature #51

Desktop (please complete the following information):

• OS: MacOS
• Version 11.4

Version of Docker Desktop:
You can find the version by clicking on the About Docker Desktop menu

3.6.0

Can't open file --list-extensions

When I click the Dev Environments
The IntelliJ IDEA will tell me like it

Desktop (please complete the following information):

• OS: macOs BigSur
• Version: 11.5.1

Version of Docker Desktop:
Docker Desktop 3.6.0 (67351) is currently the newest version available.

Cannot clone dev environment from behind company firewall

Description

When accessing a server from behind a corporate firewall using https, often self-signed certificates are used. Docker Desktop does not appear to be using the windows certificate stores and doesn't seem to have a way to add a trusted certificate.

When trying to clone you get this error:

Preparing to clone inside a volume
Installing credential helpers... done
Cloning into '/code'...
fatal: unable to access 'https://<git-url>.git': SSL certificate problem: self signed certificate in certificate chain

Steps to reproduce the issue:

1. Try to clone from a git repository over HTTPS when behind a firewall using a self-signed certificate such as a corporate firewall.

Describe the results you received:
SSL certificate problem: self signed certificate in certificate chain

Describe the results you expected:
Project clones correctly

Output of docker version:

Client:
 Cloud integration: 1.0.17
 Version:           20.10.7
 API version:       1.41
 Go version:        go1.16.4
 Git commit:        f0df350
 Built:             Wed Jun  2 12:00:56 2021
 OS/Arch:           windows/amd64
 Context:           desktop-linux
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.7
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       b0f5bc3
  Built:            Wed Jun  2 11:54:58 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.6
  GitCommit:        d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc:
  Version:          1.0.0-rc95
  GitCommit:        b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker context show:
You can also run docker context inspect context-name to give us more details but don't forget to remove sensitive content.

desktop-linux

Output of docker info:

Client:
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
  compose: Docker Compose (Docker Inc., 2.0.0-beta.4)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Containers: 10
  Running: 3
  Paused: 0
  Stopped: 7
 Images: 35
 Server Version: 20.10.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.128-microsoft-standard
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 24.91GiB
 Name: docker-desktop
 ID: ZKC6:CTO7:OUMC:UKQH:VSSO:KQGB:NK2J:EMSS:36JX:34G2:ND66:QISM
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 59
  Goroutines: 61
  System Time: 2021-06-30T20:25:12.8911353Z
  EventsListeners: 4
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled