Arch Linux User Repository

Bump to 4.43.2

Upgrades:

• Docker Compose v2.38.2
• Docker Engine v28.3.2
• Docker Model CLI v0.1.33

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, I managed to compile on the next attempt. It might have been temporary. I checked and there's a valid certificate.

@leandrocunha it seems to work fine on my end. Are you still experiencing the problem? I wonder if it was just a temporary issue. We don't have any internal alerts or known issues related to the website.

libfakeroot internal error: payload not recognized!
-> Compressing man and info pages...
==> Checking packaging issues...
==> Creating the "docker-desktop" package...
-> Generating the .PKGINFO file...
-> Generating the .BUILDINFO file...
SSL error: error:00000000:lib(0)::reason(0), a workaround might be: w3m -insecure
w3m: Can't load https://www.docker.com/legal/docker-subscription-service-agreement/.

==> ERROR: Aborted by user! Exiting...
==> Cleaning up...
-> Adding the install file...
cp: could not create common file '.INSTALL': No such file or directory
==> ERROR: Failed to add the install file to the package.

I would have to check that out...

Bump to 4.43.2

Upgrades:

• Docker Compose v2.38.2
• Docker Engine v28.3.2
• Docker Model CLI v0.1.33

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...