Open Phuurl opened 2 years ago
Hi @Phuurl, thanks for opening this issue. We'll get back to you after discussing the issue internally.
Hello @Phuurl
A quick update, we didn't fixed your issue ATM, but we at least improved the documentation for this specific point
Would this potentially cause issues such as https://github.com/docker/dev-environments/issues/137?
Why does it need to change the owner of the Docker Socket?
Describe the bug Docker Desktop creates unusable environments when using custom containers that do not create the
docker
group as part of the build.To Reproduce Steps to reproduce the behavior:
.docker/config.json
.docker/Dockerfile.devenv
This can be resolved by adding in an
addgroup
step in the Dockerfile - egExpected behavior Potential behaviours in order of preference - either: a) Docker Desktop should catch the
chown
error and transparently create the group if required b) The requirement for having the group present in custom containers should be documented on the dev environemtns guide, and the wizard should detect thechown
error and mark the step as failedDesktop (please complete the following information):
Version of Docker Desktop:
You can find the version by clicking on the
About Docker Desktop
menu