That doesn’t make any sense to me. It can be installed directly from pacman. It may be something silly like adding docker to your user group. Have you done something like below for docker?
I thought it would. If it still requires sudo to run it is probably just docker wanting your user account added to the docker group. If the “docker” group doesn’t exist you can safely create it.
You will likely need to log out and log back in for the system to recognize the new group permissions.
I use EndeavourOS, but had the same problem on Arch.
Hardware wise I have an 75800x, a RX 6700XT and 32GB 3200mhz Ram.
The weird thing is, that some time ago I was actually able to use docker, but now I’m not.
That doesn’t make any sense to me. It can be installed directly from pacman. It may be something silly like adding docker to your user group. Have you done something like below for docker?
sudo pacman -Syusudo pacman -S dockersudo systemctl enable docker.service sudo systemctl start docker.servicesudo usermod -aG docker $USERLog out and log back in for the group changes to take effect.
Verify that Docker CE is installed correctly by running:
docker --versionIf you get the above working docker compose is just
sudo pacman -S docker-composeI did all the steps you mentioned and now it works(at least if use sudo to run the commands).
I thought it would. If it still requires sudo to run it is probably just docker wanting your user account added to the docker group. If the “docker” group doesn’t exist you can safely create it.
You will likely need to log out and log back in for the system to recognize the new group permissions.
I didnt start docker and didn’t add it to my user group. Maybe this will fix it.