Arch Linux User Repository

docker-model-bin is now deprecated. Please use docker-model (source build) for the latest version and updates.

@HamzaGbada I did not suggest using sudo inside the PKGBUILD in my last update. This wasn't a message to you; it was a message for anyone who might struggle with the same issue. Relax, and thank you for maintaining this package!

Bro, you’re giving me a chronic headache.

As I have stated previously, using sudo inside a PKGBUILD is strictly prohibited and violates Arch packaging guidelines. Let me be absolutely clear: the permission errors you are encountering are caused by Docker itself, not this package. You are expected to follow the official Docker post-installation instructions here. This package does not and will never require sudo during its build or installation.

If you have a solution or workaround for Docker root/non-root issues, take it to the Docker forums here or file an issue on Docker’s GitHub here. This is not relevant to this AUR package and should not be discussed here.

My current approach to updating this package is as follows:

1. Switch the Docker context to rootless mode:

$ sudo -E docker context use rootless

1. Now, this package can be updated without issue.
2. Once updated, switch the Docker context back to the default:

$ sudo -E docker context use default

Note: The rootless context must be created in advance and should exist. I use a rootless context, but my default context is rootful. I never add normal users to the docker group on any system because it is insecure; I prefer to use sudo instead.

Hopefully, this will help someone.

@HamzaGbada Thank you, I understand your point. IMHO installing a package via an AUR helper should not produce unexpected errors. The installer should first detect the current Docker context, and if it finds a rootful context it ought to display an informative message prompting the user to take the necessary manual steps, rather than simply failing with an error.

Thanks for the feedback @diggservo

However, this isn’t an issue specific to this package — it’s a general requirement of Docker itself. According to the official Docker post-installation guide, users need to be added to the docker group in order to run Docker commands without sudo.

Using sudo inside a PKGBUILD is strongly discouraged and against Arch packaging guidelines, since makepkg runs as a non-root user by design. Privilege escalation within a PKGBUILD is considered unsafe and can lead to system-wide side effects. See the official discussion here: Arch Linux Forums – “Never use sudo inside PKGBUILD”.

In short, the permission error you encountered isn’t caused by this repository — it’s a Docker security model requirement. If you prefer not to add your user to the docker group, you can build the package inside an isolated container or VM with Docker access instead.

I understand that this package assumes we have added our user to the docker group. However, this is insanely insecure; it is equivalent to root rights.

So I suggest that you prefix every docker command with sudo. I had to do it manually; otherwise it cannot be installed, as indicated by the following error:

==> Starting build()...
Pulling docker-model image...
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.51/images/create?fromImage=docker.io%2Fdocker%2Fdocker-model-cli-desktop-module&tag=v0.1.39": dial unix /var/run/docker.sock: connect: permission denied
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: docker-model-bin-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
docker-model-bin - exit status 4