Arch Linux User Repository

Bumping to 4.43.1 with the following fixes:

• Fixed an issue that caused Docker Desktop UI to break when Ask Gordon responses contained HTML tags.
• Fixed an issue that prevented extensions from communicating with their backends.

Bump to 4.43.0

New:

• Compose Bridge is now generally available.

Upgrades:

• Upgrades
• Docker Buildx v0.25.0
• Docker Compose v2.38.1
• Docker Engine v28.3.0
• NVIDIA Container Toolkit v1.17.8

Bug fixes and enhancements:

• Fixed a bug causing docker start to drop the container's port mappings for a container already running.
• Fixed a bug that prevented container ports to be displayed on the GUI when a container was re-started.
• Fixed a bug that caused Docker API 500 Internal Server Error for API route and version error application start.
• The settings Apply & restart button is now labeled Apply. The VM is no longer restarted when applying changed settings.
• Fixed a bug where the disk would be corrupted if Docker is shutdown during a fsck.
• Fixed a bug causing an incorrect ~/.kube/config in WSL2 when using a kind Kubernetes cluster.
• Return an explicit error to a Docker API / docker CLI command if Docker Desktop has been manually paused.
• Fixed an issue where unknown keys in Admin and Cloud settings caused a failure.

Bug fixes and enhancements for AUR package:

• Installation no longer fails if systemd is not present.
• Docker Desktop will only restart upon upgrades if the user has explicitly enabled the service.
• Enabled usage of privileged ports.
• Added kubernetes.docker.internal to the hosts list.

EDIT: Removed note about bumping virtiofsd

rmunn, Dear all, the docker-desktop package provided here is the same one available upstream and we still have xeeynamo, an employee of the Docker company who makes the software available, provides updates and solves the problems found. It is also up to whoever provides new updates to update the .install if necessary (xeeynamo, check this for us, please). ;)

Bumping to 4.43.1 with the following fixes:

• Fixed an issue that caused Docker Desktop UI to break when Ask Gordon responses contained HTML tags.
• Fixed an issue that prevented extensions from communicating with their backends.

Bump to 4.43.0

New:

• Compose Bridge is now generally available.

Upgrades:

• Upgrades
• Docker Buildx v0.25.0
• Docker Compose v2.38.1
• Docker Engine v28.3.0
• NVIDIA Container Toolkit v1.17.8

Bug fixes and enhancements:

• Fixed a bug causing docker start to drop the container's port mappings for a container already running.
• Fixed a bug that prevented container ports to be displayed on the GUI when a container was re-started.
• Fixed a bug that caused Docker API 500 Internal Server Error for API route and version error application start.
• The settings Apply & restart button is now labeled Apply. The VM is no longer restarted when applying changed settings.
• Fixed a bug where the disk would be corrupted if Docker is shutdown during a fsck.
• Fixed a bug causing an incorrect ~/.kube/config in WSL2 when using a kind Kubernetes cluster.
• Return an explicit error to a Docker API / docker CLI command if Docker Desktop has been manually paused.
• Fixed an issue where unknown keys in Admin and Cloud settings caused a failure.

Bug fixes and enhancements for AUR package:

• Installation no longer fails if systemd is not present.
• Docker Desktop will only restart upon upgrades if the user has explicitly enabled the service.
• Enabled usage of privileged ports.
• Added kubernetes.docker.internal to the hosts list.

EDIT: Removed note about bumping virtiofsd

@xeeynamo - The two small changes that would fix my issue would be for the AUR's PKGBUILD to run the setcap line to enable the use of privileged ports, and to ensure the kubernetes.docker.internal line gets added to /etc/hosts if it isn't there. Those two steps, if they can make it into a 4.43.0 release of the AUR package, would allow me to use the AUR package again rather than manually downloading the upstream package.

Would you like me to open a GitHub issue at https://github.com/docker/for-linux/issues to track this? I'll wait until I hear from you before opening that issue, so as not to make more work for you if it's not necessary.

@leandrocunha - Yes, it's the same package, the only issue is that the PKGBUILD doesn't point to the .INSTALL file from the original package but instead points to an install script (docker-desktop.install from the AUR Git repo) that doesn't quite have the same behavior in the post-install steps as the .INSTALL file from the upstream package. The lack of the "setcap cap_net_bind_service,cap_sys_resource=+ep /opt/docker-desktop/bin/com.docker.backend" is the specific cause of the problems I was having — and that's part of the PKGBUILD (and associated docker-desktop.install script). The rest of the files are the same as the upstream package, it's only the post-install step that differs (and which caused my issue).

Hey @rmunn, there are indeed some minor oddities and inconsistencies between the Docker-distributed package and the one in AUR. I decided to keep things as they were and limited my changes to just bumping the Docker Desktop version. This was to respect the original submitter and maintainers, and to avoid introducing any unintended breaking changes. But I'm happy to work on aligning the two packages to reduce the maintenance burden and improve consistency if needed.

We’re about to release version 4.43.0, and I can include some subtle improvements to the AUR package based on your suggestions. However, I will need a bit more time to work toward a more comprehensive, long-term solution.

@Nyyr, could you please open an issue at https://github.com/docker/for-linux/issues and include a Diagnostic ID? I’ll be happy to help you there.

rmunn, Dear all, the docker-desktop package provided here is the same one available upstream and we still have xeeynamo, an employee of the Docker company who makes the software available, provides updates and solves the problems found. It is also up to whoever provides new updates to update the .install if necessary (xeeynamo, check this for us, please). ;)

running engine: waiting for the Docker API: engine linux/qemu failed to run: running VM: qemu: process terminated unexpectedly: exit status 1

It seems the install script didn't do its job...

What (part of) the pacman output should look like when installing the docker-desktop package:

:: Processing package changes...
(1/1) reinstalling docker-desktop
Enabling use of privileged ports by Docker Desktop
kubernetes.docker.internal already in /etc/hosts
Reloading systemd daemon for logged in users
Done reloading systemd daemon for logged in users
:: Running post-transaction hooks...

What I got from running this PKGBUILD:

:: Processing package changes...
(1/2) reinstalling docker-desktop
(2/2) installing docker-desktop-debug
:: Running post-transaction hooks...

The post_install and post_upgrade scripts in this PKGBUILD's docker-desktop.install script do not match the behavior of the .INSTALL file included in the upstream-provided package. They don't echo anything to the console to show what they're doing (very minor), and they don't run the steps that .INSTALL does (which was a big problem for me, as my local k8s setup relies in the ingress container binding to localhost port 80). The steps should be as follows:

• run setpcap to allow Docker containers to bind to ports below 1024
• add a kubernetes.docker.internal entry to /etc/hosts
• create symlinks in /usr/local/bin/docker and /usr/local/bin/compose-bridge to accommodate any scripts that have hardcoded those locations
• run update-desktop-database to pick up the .desktop files that went into /usr/share/appliucations
• run systemctl daemon-reload so it will pick up on the maybe-newly-installed unit files

The upstream-provided package runs all those steps for both post_install and post_upgrade. It's possible that some could be skipped for post_upgrade, like running systemctl daemon-reload, but just to be safe it's probably best for this AUR PKGBUILD to run all the same steps that upstream does. Then you won't see differences in behavior, like I did, between running the AUR package and installing the upstream package.

Package currently fails to run post-install steps, which means (among other things) that Docker containers can't bind to port 80. I spent almost two days wondering why my k8s ingress was failing before I solved it by accident by reinstalling from the Docker Desktop official package rather than this AUR package.

In the package available from https://desktop.docker.com/linux/main/amd64/196648/docker-desktop-x86_64.pkg.tar.zst there is a .INSTALL file which, among other things, contains the following in the post_install step:

echo 'Enabling use of privileged ports by Docker Desktop'
setcap cap_net_bind_service,cap_sys_resource=+ep /opt/docker-desktop/bin/com.docker.backend || echo 'Error: Docker Desktop will not be able to bind to privileged ports'

That step, and a couple others like adding 127.0.0.1 kubernetes.docker.internal to /etc/hosts, is missing from the PKGBUILD of this AUR.

Bumped to Docker Desktop 4.42.1:

Upgrades

• Docker Compose v2.37.1

Bug fixes

• Fixed an issue where Docker domains were not reachable when the proxy configuration is not valid.
• Fixed a possible deadlock when exposing ports.
• Fixed a race condition which can cause docker run -p ports to disappear.

@erdnuesse I agree with the sentiment. When updating a package, the related application should not start with it. We are preparing to release 4.42.1 soon and I will be sure to include your suggestion in the next package release.