SOLVED: Container Not Launching

[jkboi]

It doesn't seem like docker is installed.  Docker compose seems to be though

jkboyo@limitedpower:/srv/appdata/jellyfin$ sudo systemctl status docker
[sudo] password for jkboyo:
Unit docker.service could not be found.
jkboyo@limitedpower:/srv/appdata/jellyfin$ sudo apt list --installed | grep docker

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.


This is what I get when I do docker compose version

jkboyo@limitedpower:/srv/appdata/jellyfin$ docker compose version
Docker Compose version v2.20.3

and then when I do docker --version I get this

jkboyo@limitedpower:/srv/appdata/jellyfin$ docker --version
Docker version 24.0.5, build ced0996

So I dunno why it isn't showing anything.

Do I have to activate it somehow?

[AGiLiT]

This has nothing to do with that. This is a brand spanking new container on a server that hasn't had JF b4.  

The error is actually docker related I'm just having trouble finding the reason I can't get the container to launch.

Not so sure it's not related.  You could test by changing your install script where it says 'jellyfin:latest' to jellyfin:10.8.13' and seeing what happens...

[jkboi]

This has nothing to do with that. This is a brand spanking new container on a server that hasn't had JF b4.  

The error is actually docker related I'm just having trouble finding the reason I can't get the container to launch.

Not so sure it's not related.  You could test by changing your install script where it says 'jellyfin:latest' to jellyfin:10.8.13' and seeing what happens...

It isn't. Nothing docker related is working. I am able to connect to my 10.9 instance on another server I just do not know how to setup docker compose successfully.

[jkboi]

So I think the issue is it seems docker is installed through snap for some reason instead of apt.

Should I uninstall and reinstall through apt so stuff matches or just leave it as is?

[Efficient_Good_5784]

Not so sure it's not related.  You could test by changing your install script where it says 'jellyfin:latest' to jellyfin:10.8.13' and seeing what happens...

This sounds like a different issue than what the OP is facing.

You updated to v10.9.# and one of your clients is refusing to connect.
If you're not able to solve that, please open a new thread to see if anyone can provide you with help on how to fix that issue.

The issue in this thread is that @jkboi can't get the container to launch with Docker. The Jellyfin version shouldn't matter here as:

1. There is no previous version that is being migrated to a new container
   
2. The latest v10.9 releases work well with Docker
   

[TheDreadPirate]

Uninstall the snap and follow Docker's docs to install via apt. Add their repo then install docker engine. You will also need to install the docker compose plugin.

https://docs.docker.com/engine/install/ubuntu/

[jkboi]

Uninstall the snap and follow Docker's docs to install via apt.  Add their repo then install docker engine.  You will also need to install the docker compose plugin.

https://docs.docker.com/engine/install/ubuntu/

It is getting somewhere now!!!!!! Thank you so much for your help! I am now getting this permissions error.

jkboyo@limitedpower:/srv/appdata/jellyfin$ docker compose up
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.46/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%3Djellyfin%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied

you did fix my main issue now though so thank you!

---

It launched when I ran it with sudo. Is this something I should change with a permission or something or should I always sudo docker compose up

[TheDreadPirate]

There will be a "docker" group. Add your user to the docker group then you don't have to use sudo for docker commands. You will have to log out and log back in for the change to take affect.

[jkboi]

There will be a "docker" group.  Add your user to the docker group then you don't have to use sudo for docker commands.  You will have to log out and log back in for the change to take affect.

Thank you again so much! I was bashing my head against a wall it felt trying to test everything! I appreciate the help!