{"id":1195,"date":"2024-09-03T18:56:03","date_gmt":"2024-09-03T18:56:03","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2024\/09\/03\/docker-desktop-4-34-msi-installer-ga-upgraded-host-networking-and-powerful-enhancements-for-boosted-productivity-administration\/"},"modified":"2024-09-03T18:56:03","modified_gmt":"2024-09-03T18:56:03","slug":"docker-desktop-4-34-msi-installer-ga-upgraded-host-networking-and-powerful-enhancements-for-boosted-productivity-administration","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2024\/09\/03\/docker-desktop-4-34-msi-installer-ga-upgraded-host-networking-and-powerful-enhancements-for-boosted-productivity-administration\/","title":{"rendered":"Docker Desktop 4.34: MSI Installer GA, Upgraded Host Networking, and Powerful Enhancements for Boosted Productivity & Administration"},"content":{"rendered":"

Key GA features of the Docker Desktop 4.34 release include:\u00a0<\/strong><\/p>\n

MSI installer GA and Windows registry key<\/a>\u00a0<\/p>\n

Host networking support to Docker Desktop\u00a0<\/a><\/p>\n

Automatic reclamation of disk space in Docker Desktop for WSL2<\/a><\/p>\n

Authentication enhancements\u00a0<\/a><\/p>\n

NVIDIA AI Workbench Docker Desktop Integration\u00a0<\/a><\/p>\n

Multi-platform UX improvements and the containerd image store<\/a><\/p>\n

Docker Desktop 4.34<\/a> introduces key features to enhance security, scalability, and productivity for all development team sizes, making deploying and managing environments more straightforward. With the general availability (GA) of the MSI installer for bulk deployment, managing installations across Windows environments becomes even simpler. Enhanced authentication features offer an improved administration experience while reinforcing security. Automatically reclaim valuable disk space with Docker Desktop\u2019s new smart compaction feature, streamlining storage management for WSL2 users. Additionally, the integration with NVIDIA AI Workbench provides developers with a seamless connection between model training and local development. Explore how these innovations simplify your workflows and foster a culture of innovation and reliability in your development practices.<\/p>\n

Deploy Docker Desktop in bulk with the MSI installer<\/h2>\n

We\u2019re excited to announce that the MSI installer for Docker Desktop<\/a> is now generally available to all our Docker Business customers. This powerful tool allows you to customize and deploy Docker Desktop across multiple users or machines in an enterprise environment, making it easier to manage Docker at scale.\u00a0<\/p>\n

Features include:<\/p>\n

Interactive and silent installations: Choose between an interactive setup process or deploy silently across your organization without interrupting your users.<\/p>\n

Customizable installation paths: Tailor the installation location to fit your organization\u2019s needs.<\/p>\n

Desktop shortcuts and automatic startup: Simplify access for users with automatic creation of desktop shortcuts and Docker Desktop starting automatically after installation.<\/p>\n

Set usage to specific Docker Hub organizations: Control which Docker Hub organizations your users are tied to during installation.<\/p>\n

Docker administrators can download the MSI installer directly from the Docker Admin Console<\/a>.<\/p>\n

One of the standout features of this installer is the –allowed-org flag. This option enables the creation of a Windows registry key during installation, enforcing sign-in to a specified organization. By requiring sign-in, you ensure that your developers are using Docker Desktop with their corporate credentials, fully leveraging your Docker Business subscription. This also adds an extra layer of security, protecting your software supply chain.<\/p>\n

Additionally, this feature paves the way for Docker to provide you with valuable usage insights across your organization and enable cloud-based control over application settings for every user in your organization in the future.<\/p>\n

<\/a>Figure 1: Docker admins can download the MSI installer directly from the Docker Admin Console.<\/p>\n

What\u2019s next<\/h3>\n

We\u2019re also working on releasing a PKG enterprise installer for macOS, config profiles for macOS, and supporting multiple organizations in all supported sign-in enforcement mechanisms.\u00a0<\/p>\n

Refer to our docs to learn about MSI configuration<\/a> and discover more about sign-in enforcement via Windows registry key<\/a>.<\/p>\n

Host networking support to Docker Desktop\u00a0<\/h2>\n

Previously, Docker Desktop lacked seamless host networking capability, complicating the integration between host and container network services. Developers had to take time to set up and enable communication between the host and containers. Docker Desktop now supports host networking capability directly into Docker Desktop.\u00a0<\/p>\n

Host networking allows containers that are started with –net=host to use localhost to connect to TCP and UDP services on the host. It will automatically allow software on the host to use localhost to connect to TCP and UDP services in the container. This simplifies the setup for scenarios in which close integration between host and container network services is required. Additionally, we\u2019re driving cross-platform consistency and simplifying configuration by reducing the need for additional steps, such as setting up port forwarding or bridge networks.\u00a0<\/p>\n

While this has previously been available in the Docker Engine, we\u2019re now extending this capability to Docker Desktop for Windows, macOS, and Linux. We\u2019re dedicated to improving developer productivity, and this is another way we help developers spend less time configuring network settings and more time building and testing applications, accelerating development cycles.\u00a0<\/p>\n

This new capability is available for all users logged into Docker Desktop. To enable this feature, navigate to Settings > Resources > Network.<\/strong> Learn more about this feature on Docker Docs.\u00a0<\/a><\/p>\n

<\/a>Figure 2: Enable the host networking support feature in the Settings menu.<\/p>\n

Automatic reclamation of disk space in Docker Desktop for WSL2\u00a0<\/h2>\n

Previously, when customers using Docker Desktop for WSL2 deleted Docker objects such as containers, images, or builds (for example via a docker system prune), the freed storage space was not automatically reclaimed on their host. Instead, they had to use external tools to \u201ccompact\u201d the virtual disk\/distribution backing Docker Desktop.<\/p>\n

Starting with Docker 4.34, we are rolling out automatic reclamation of disk space. When you quit the app, Docker Desktop will automatically check whether there is storage space that can be returned to the host. It will then scan the virtual disk used for Docker storage, and compact it by returning all zeroed blocks to the operating system. Currently Docker Desktop will only start the scan when it estimates that at least 16GB of space can be returned. In the future, we plan to make this threshold adaptive and configurable by the user.<\/p>\n

The feature is now enabled for all customers running the Mono distribution architecture for Docker Desktop on WSL2. This new architecture, which was rolled out starting with Docker Desktop 4.30 for all fresh installations of Docker Desktop, removed the need for a dedicated docker-desktop-data WSL2 distribution to store docker data. We will be rolling out the new architecture to all customers in the upcoming Docker Desktop releases.<\/p>\n

Customers with installations still using the docker-desktop-data WSL2 distribution can compact storage manually via VHDX compaction tools<\/a>, or change the WSL2 configuration to enable the experimental WSL2 feature<\/a> for disk cleanup.<\/p>\n

(Pro tip: <\/strong>Did you know you can use the Disk Usage extension<\/a> to see how Docker Desktop is using your storage and use it to prune dangling objects with a single click?)<\/p>\n

Authentication enhancements\u00a0<\/h2>\n

Previously, authenticating via the CLI required developers to either type their password into the command-line interface \u2014 which should generally be avoided by the security-minded \u2014 or manually create a personal access token<\/a> (PAT) by navigating to their Docker account settings, generating the token, and then copying it into the CLI for authentication. This process was time-consuming and forced developers to switch contexts between the CLI and the web portal.<\/p>\n

In this latest Docker Desktop release, we\u2019re streamlining the CLI authentication flow. Now, users can authenticate through a seamless browser-based process, similar to the experience in CLIs like GitHub\u2019s gh or Amazon\u2019s AWS CLI. With this improved flow, typing docker login in the CLI will print a confirmation code and open your browser for authentication, automating PAT creation behind the scenes and eliminating the need for manual PAT provisioning. This enhancement saves time, reduces complexity, and delivers a smoother and more secure user experience. Additionally, when you authenticate using this workflow, you\u2019ll be logged in across both Docker CLI and Docker Desktop.\u00a0<\/p>\n

This new flow also supports developers in organizations that require single sign-on (SSO), ensuring a consistent and secure authentication process.<\/p>\n

<\/a>Figure 3: When you log in via the new workflow, you\u2019ll be logged in across both Docker CLI and Docker Desktop.<\/p>\n

Enterprise-grade AI application development with Docker Desktop and NVIDIA AI Workbench\u00a0\u00a0<\/h2>\n

AI development is a complex journey, often hindered by the challenge of connecting the dots between model training, local development, and deployment. Developers frequently encounter a fragmented and inconsistent development environment and toolchain, making it difficult to move seamlessly from training models in the cloud to running them locally. This fragmentation slows down innovation, introduces errors, and complicates the end-to-end development process.<\/p>\n

To solve this, we\u2019re proud to announce the integration of Docker Desktop with NVIDIA AI Workbench<\/a>, a collaboration designed to streamline every stage of AI development. This solution brings together the power of Docker\u2019s containerization with NVIDIA\u2019s leading AI tools, providing a unified environment that bridges the gap between model training and local development.<\/p>\n

With this integration, you can now train models in the cloud using NVIDIA\u2019s robust toolkit and effortlessly transition to local development on Docker Desktop. This eliminates the friction of managing different environments and configurations, enabling a smoother, more efficient workflow from start to finish.\u00a0<\/p>\n

To learn more about this collaboration and how Docker Business supports enterprise-grade AI application development, read our blog post.\u00a0<\/a><\/p>\n

Multi-platform UX improvements and the containerd image store\u00a0\u00a0<\/h2>\n

In February 2024, we announced<\/a> the general availability of the containerd image store in Docker Desktop. Since then, we\u2019ve been working on improving the output of our commands to make multi-platform images easier to view and manage.\u00a0<\/p>\n

Now, we are happy to announce that the docker image list CLI command now supports an experimental –tree flag. This offers a completely new tree view of the image list, which is more suitable for describing multi-platform images.<\/p>\n

Figure 4: New CLI tree view of the image list.<\/p>\n

If you\u2019re looking for multi-platform support, you need to ensure that you have the containerd image store enabled in Docker Desktop (see General<\/strong> settings in Docker Desktop, select Use containerd for pulling and storing images<\/strong>). As of the Docker Desktop 4.34 release, fresh installs or factory resets of Docker Desktop will now default to using the containerd image store, meaning that you get multi-platform building capability out of the box.\u00a0<\/p>\n

Figure 5: You can enable the containerd image store in the Docker Desktop general settings.<\/p>\n

To learn more about the containerd image store, check out our containerd documentation<\/a>.\u00a0<\/a><\/p>\n

Wrapping up\u00a0<\/h2>\n

Docker Desktop 4.34 marks a significant milestone in our commitment to providing an industry-leading container development suite. With key features such as the MSI installer for bulk deployment, enhanced authentication mechanisms, and the integration with NVIDIA AI Workbench, Docker Desktop is transforming how teams manage deployments, protect their environments, and accelerate their development workflows.\u00a0<\/p>\n

These advancements simplify your development processes and help drive a culture of innovation and reliability. Stay tuned for more exciting updates and enhancements as we continue to deliver solutions designed to empower your development teams and secure your operations at scale.\u00a0<\/p>\n

Upgrade to Docker Desktop 4.34<\/a> today and experience the future of container development.\u00a0<\/p>\n

Learn more<\/h2>\n

Authenticate and update<\/a> to receive your subscription level\u2019s newest Docker Desktop features.<\/p>\n

New to Docker? Create an account<\/a>.\u00a0<\/p>\n

Subscribe to the Docker Newsletter<\/a>.<\/p>\n

Read New Docker Desktop Enterprise Admin Features: MSI Installer and Login Enforcement Alternative<\/a>.\u00a0<\/p>\n

Read Optimizing AI Application Development with Docker Desktop and NVIDIA AI Workbench<\/a>.\u00a0<\/p>\n

Learn more about MSI configuration<\/a>.<\/p>\n

Discover more about sign-in enforcement via Windows registry key<\/a>.<\/p>\n

Learn more about host networking support<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"

Key GA features of the Docker Desktop 4.34 release include:\u00a0 MSI installer GA and Windows registry key\u00a0 Host networking support […]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[4],"tags":[],"class_list":["post-1195","post","type-post","status-publish","format-standard","hentry","category-docker"],"_links":{"self":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/1195","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/comments?post=1195"}],"version-history":[{"count":0,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/1195\/revisions"}],"wp:attachment":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/media?parent=1195"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/categories?post=1195"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/tags?post=1195"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}