Docker Desktop 3.6 has just been released and we’re looking forward to you trying it. Start Dev Environments from your Local Machine You can now share dev environments with your colleagues and get started with code already on your local machine as well as the existing remote repository support. It’s easy to use your local […]
Docker Desktop 3.6 has just been released and we’re looking forward to you trying it.
You can now share dev environments with your colleagues and get started with code already on your local machine as well as the existing remote repository support.
It’s easy to use your local code! Just click Create in the top right corner of the dev environments page.
Next select the Local tab and click Select directory to open the root of the code that you would like to work on.
Finally, click Create. This creates a Dev Environment using your local folder, and bind-mounts your local code in the Dev Environment. It opens VS Code inside the Dev Environment container.
We are excited that you are trying out our Dev Environments Preview and would love to hear from you! Let us know your feedback by creating an issue in the Dev Environments GitHub repository. Alternatively, get in touch with us on the #docker-dev-environments channel in the Docker Community Slack.
We know that volumes can take up a lot of disk space, but when you’re dealing with a lot of volumes, it can be hard to find which ones you want to clean up. In 3.6 we’ve made it easier to find and sort your volumes. You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the search field.
We’re continuing to enhance volume management and would love your input. Have ideas on how we might make managing volumes easier? Interested in sharing your volumes with colleagues? Let us know here.
A first Release Candidate for Compose V2 is now available! We’ve been working hard to address all your feedback so that you can seamlessly run the compose command in the Docker CLI. Let us know your feedback on the new ‘compose’ command by creating an issue in the Compose-CLI GitHub repository.
We have also introduced the following new features:
docker-compose logs --followwhich makes it easier to follow logs of new containers. This reacts to containers added by
scaleand reports additional logs when more containers are added to
You can test this new functionality by running the
docker compose command, dropping the – in
docker-compose. We are continuing to roll this out gradually; 54% of compose users are already using compose V2. You’ll be notified if you are using the new
docker compose. You can opt-in to run Compose v2 with docker-compose, by running
docker-compose enable-v2 command or by updating your Docker Desktop’s Experimental Features settings.
If you run into any issues using Compose V2, simply run
docker-compose disable-v2 command, or turn it off using Docker Desktop’s Experimental Features.
To get started simply download or update to Docker Desktop 3.6. If you’d like to dig deeper into your volumes or take your collaboration to the next level with dev environments, upgrade to a Pro or Team subscription today!
The post Start Dev Environments locally, Compose V2 RC 1, and more in Docker Desktop 3.6 appeared first on Docker Blog.