Arch Linux User Repository

@kakawait Maybe I didn't understand -- if you're using rootless docker, why would you use sudo?

I didn't customize the docker.socket unit file -- this was only when trying to shut down the systemd user-level docker service, something like this:

systemd --user stop docker (which can hang)

systemd -- user stop --now docker.socket (which cleared the hang for me IIRC)

There's a big difference between the docker unit available at the system level and the one available at the user level -- systemd stop docker !== systemd --user stop docker

[EDIT] - I fixed my issue with the ENV, it was indeed .bashrc and my issue was that I launched startx from a shell that had DOCKER_HOST set (so every shell created there-in was inheriting the variable from the initial shell, despite .bashrc being updated to remove the variable).

@t3hmrman thus you've customized the docker.socket systemd unit file? To add --now?

Otherwise no issue with the env but to be honest I always let it set. When I want to use non rootless docker I'm using sudo

@kakawait I find that stopping the service works properly if I also stop docker.socket with the --now parameter. Stopping the service itself hangs and from another shell I stop the socket.

Possibly unrelated to that, has anyone had an issue with DOCKER_HOST remaining modified after removing docker rootless mode? In particular I find that something is still setting DOCKER_HOST to unix:///run/user/1000/docker.sock. I've removed the export from my .bashrc of course, and can't find anywhere else in the usual ENV modification locations that could be setting it. The service (both system and user level) are off as well.

[EDIT] - I fixed my issue with the ENV, it was indeed .bashrc and my issue was that I launched startx from a shell that had DOCKER_HOST set (so every shell created there-in was inheriting the variable from the initial shell, despite .bashrc being updated to remove the variable).

Do you have any issue when stopping service with systemd? In my side is stucking even after few mins. But docker seems to be stopped because docker ps returns

Cannot connect to the Docker daemon at unix:///run/user/1000/docker.sock. Is the docker daemon running?

@WhyNotHugo Sorry, I missed to find .install file.

I was unaware of /usr/lib/sysctl.d/. I've updated the PKGBUILD to use that location instead.

Regarding the install file, that's included with all the instructions. See https://aur.archlinux.org/cgit/aur.git/tree/docker-rootless-extras-bin.install?h=docker-rootless-extras-bin

Note that this is not visible on post-update, so maybe that's why you missed it?

This package needs to setting post install at user.
I suggest to show some message at post_install() like this.

Hello. Many package was putting sysctl file under /usr/lib/sysctl.d/ dir. Please move /etc/sysctl.d/99-docker-rootless.conf to /usr/lib/sysctl.d/99-docker-rootless.conf.

Hi! Do you mind including this files as docker.socket too?

[Unit]
Description=Docker Socket for the API

[Socket]
ListenStream=%t/docker.sock
SocketMode=0660

[Install]
WantedBy=sockets.target

With this file, one can run systemctl --user enable --now docker.socket, and docker will auto-start on demand (like the system docker). %t expands to $XDG_RUNTIME_DIR; this follows upstream's recommended path for the socket, at matches the one on your instructions now).

post_install Setup for docker-rootless-extras

Setup on your userspace, i,e exec this command and following instruction.

  $ dockerd-rootless-setuptool.sh check

systemd Setup for docker-rootless-extras

Start rootless docker with systemd.

  $ systemctl start --user dockerd-rootless.service

To launch the daemon on system startup.

  $ systemctl enable --user dockerd-rootless.service

Exec docker command on docker-rootless-extras

Following this commands.

  $ export DOCKER_HOST=unix:///run/user/1000/docker.sock
  $ docker info