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 and docker-compose installed; I was already in the docker group; and the service was already active per systemctl. 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 and top | grep docker tell me dockerd is running by root. 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 without sudo 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 by top and ps. 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.
OK, well that works enough to access the specified port and loads the webapp. So that’s cool. :) There’s a tcp error printed in the page itself but ?maybe? that is caused by improperly running it.
It could well be some self imposed error. But I’m always gonna be making those. If it is, it happened because I was trying to solve some other rudimentary issue. I’ve never gotten anything functional with this so it’s not like I was trying to do something fancy and got in over my head.
Part of the issue with docker in this attempt and other times is it doesn’t give good enough errors/output to diagnose. It’s really kind of you to help me here but I can’t call you every step. The documentation is too focused on making things look simple even when they’re not, and therefor glossing over whatever system weirdies are getting in the way. You identified a user issue and even I suspected it (that’s why I tried all those commands with and without
sudoin the above comment). Yet it is not in the official documentation as a potential cause of said error. And now that I have confirmed it, I have no idea how to solve it. I see in my browser history I’ve previously looked up “rootless mode”. Maybe that’s how I screwed this up in the first place.Moral of the story is, docker becomes a mess immediately. :D