I wish more projects would have cheap rate subscriptions. Bitwarden was my first floss subscription and I don’t even consider canceling it even though I don’t really need any of the premium features. (I think its more like 1€ per month.)
But these “its the price of a fancy coffee per month” ones… Girl I haven’t had a fancy coffee since like 2018.
I really appreciate the time you took to help me but seriously there is always issues even when it’s supposed to be simple/basic. Nevertheless I am in the mood to be wrong and pleasantly surprised so I follow your instructions. (Spoiler: It doesn’t work. But I am not trying to request further help about this, because I am fairly resigned to the situation. I am just showing you, that I tried.)
I already had
docker
anddocker-compose
installed; I was already in thedocker
group; and the service was already active persystemctl
. I guess from last time I tried this (not too long ago). Create directory, file etc.$ docker compose up unable to get image 'zefhemel/silverbullet': Cannot connect to the Docker daemon at unix:///home/username/.docker/run/docker.sock. Is the docker daemon running?
So I find Troubleshooting the Docker daemon | Docker Docs. It has several methods to find out if docker is even running which now I am confused about.
reports as inactive:
# systemctl is-active docker
,# systemctl status docker.service
,$ docker info
report as active:
$ systemctl status docker.service
,# systemctl is-active docker
,$ systemctl is-active docker
,# docker info
$ env | grep DOCKER_HOST
and# env | grep DOCKER_HOST
have no output.ps aux | grep docker
andtop | grep docker
tell medockerd
is running byroot
. So I think maybe I need to start it as a regular user for this exercise?Found Start the daemon | Docker Docs which advises the use of
dockerd
either with or withoutsudo
depending on environment.normal user:
Starting up dockerd needs to be started with root privileges. To run dockerd in rootless mode as an unprivileged user, see https://docs.docker.com/go/rootless/
Oh it needs to be root. OK, try again with sudo:
Starting up failed to start daemon, ensure docker is not running or delete /var/run/docker.pid: process with PID 3952 is still running
So it is running?
3952
was pid reported bytop
andps
. It is running. But it’s not running.Who knows… honestly this is how it goes every time. Maybe I am running services wrong… maybe I set something up last time because I was trying to solve another problem and it was suggested and that thing is now causing me am issue. I could chase my tail on this all week.
Like I said I completely believe everyone that once you’re rolling with it, it’s great. I’m happy for everyone who is able to access this. I will continue to live without it for the time being.