I have installed jellyfin and went to start and enable it’s service and it will not start or enable. I thought it just might be jellyfin son I decided to install Docker and got the same thing. I’ve rebooted to see if that would fix the issue but no it’s still the same. Thoughts on getting this fixed? Thanks
locutus@localhost:~> sudo systemctl enable docker
[sudo] password for root:
Failed to enable unit: Unit file docker.service does not exist.
locutus@localhost:~> sudo groupadd docker
locutus@localhost:~> sudo gpasswd -a $USER docker
Adding user locutus to group docker
locutus@localhost:~> newgrp docker
locutus@localhost:~> docker pull ubuntu
If 'docker' is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf docker
locutus@localhost:~> sudo systemctl enable docker
Failed to enable unit: Unit file docker.service does not exist.
locutus@localhost:~> sudo systemctl start docker
Failed to start docker.service: Unit docker.service not found.
locutus@localhost:~>
Start with
zypper se docker
to see what is available/installed
https://en.opensuse.org/Docker
I’d like to avoid docker. To me it’s an extra layer that’s simply unnecessary.
locutus@localhost:~> sudo zypper se docker
[sudo] password for root:
Retrieving repository 'Education' metadata .......................................................................[done]
Building repository 'Education' cache ............................................................................[done]
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+---------------------------------------+----------------------------------------------------------------+-----------
| bumblebee-status-module-docker-ps | Widget for docker containers running | package
| docker | The Moby-project Linux container runtime | package
| docker-bash-completion | Bash Completion for docker | package
| docker-bench-security | Docker Bench for Security | package
| docker-buildx | Docker CLI plugin for extended build capabilities with Build-> | package
| docker-client-java | Docker Client | package
| docker-client-java | Docker Client | srcpackage
| docker-client-java-javadoc | Javadoc for docker-client-java | package
| docker-distribution-registry | Registry server for Docker | package
| docker-fish-completion | Fish completion for docker | package
| docker-kubic | The Moby-project Linux container runtime | package
| docker-kubic-bash-completion | Bash Completion for docker-kubic | package
| docker-kubic-fish-completion | Fish completion for docker-kubic | package
| docker-kubic-kubeadm-criconfig | docker container runtime configuration for kubeadm | package
| docker-kubic-zsh-completion | Zsh Completion for docker-kubic | package
| docker-lock | Automatically manage image digests in Dockerfiles, docker-co-> | package
| docker-machine-driver-kvm2 | KVM driver for docker-machine | package
| docker-zsh-completion | Zsh Completion for docker | package
| docker_auth | Authenticaton for container registry with tokens | package
| obs-service-docker_label_helper | OBS Service to add prefixed labels in Dockerfile builds | package
| openSUSE-release-appliance-docker | openSUSE Tumbleweed | package
| openscap-docker | Docker plugin for OpenSCAP | package
| ovn-docker | Docker network plugins for OVN | package
| pcp-pmda-docker | Performance Co-Pilot (PCP) metrics from the Docker daemon | package
| podman-docker | Emulate Docker CLI using podman | package
| python3-avocado-plugins-runner-docker | Avocado Runner for Execution on Docker Containers | package
i | python310-docker | Docker API Client | package
i+ | python310-docker-compose | Tool to define and run complex applications using Docker | package
i | python310-docker-pycreds | Python bindings for the Docker credentials store API | package
i | python310-dockerpty | Docker API Client | package
| python38-docker | Docker API Client | package
| python38-docker-compose | Tool to define and run complex applications using Docker | package
| python38-docker-pycreds | Python bindings for the Docker credentials store API | package
| python38-dockerpty | Docker API Client | package
| python39-docker | Docker API Client | package
| python39-docker-compose | Tool to define and run complex applications using Docker | package
| python39-docker-pycreds | Python bindings for the Docker credentials store API | package
| python39-dockerpty | Docker API Client | package
| rubygem-docker-api | A simple REST client for the Docker Remote API | package
| rubygem-docker-api-doc | RDoc documentation for docker-api | package
| rubygem-docker-api-testsuite | Test suite for docker-api | package
| yast2-docker | YaST2 - GUI for docker management | package
locutus@localhost:~>
locutus@localhost:~> sudo zypper install docker python3-docker-compose
[sudo] password for root:
Sorry, try again.
[sudo] password for root:
Loading repository data...
Reading installed packages...
'python3-docker-compose' not found in package names. Trying capabilities.
Resolving package dependencies...
The following 2 recommended packages were automatically selected:
python38-gssapi python38-invoke
The following 23 NEW packages are going to be installed:
containerd docker docker-bash-completion python38-click python38-docker python38-docker-compose python38-dockerpty
python38-docker-pycreds python38-docopt python38-fluidity-sm python38-gssapi python38-importlib-resources
python38-invoke python38-jsonschema python38-lexicon python38-paramiko python38-pexpect python38-ptyprocess
python38-PyNaCl python38-pyrsistent python38-python-dotenv python38-PyYAML python38-websocket-client
23 new packages to install.
Overall download size: 49.0 MiB. Already cached: 0 B. After the operation, additional 216.4 MiB will be used.
**Continue? [y/n/v/...? shows all options] (y): **y
Retrieving package containerd-1.5.11-1.2.x86_64 (1/23), 16.9 MiB ( 72.8 MiB unpacked)
Retrieving: containerd-1.5.11-1.2.x86_64.rpm .........................................................[done (4.0 MiB/s)]
Retrieving package python38-PyNaCl-1.5.0-1.2.x86_64 (2/23), 113.2 KiB (650.2 KiB unpacked)
Retrieving: python38-PyNaCl-1.5.0-1.2.x86_64.rpm .................................................................[done]
Retrieving package python38-PyYAML-6.0-2.3.x86_64 (3/23), 112.0 KiB (551.3 KiB unpacked)
Retrieving: python38-PyYAML-6.0-2.3.x86_64.rpm ...................................................................[done]
Retrieving package python38-click-8.0.4-1.3.noarch (4/23), 192.9 KiB (953.8 KiB unpacked)
Retrieving: python38-click-8.0.4-1.3.noarch.rpm ..................................................................[done]
Retrieving package python38-docker-pycreds-0.4.0-1.14.noarch (5/23), 22.2 KiB ( 31.2 KiB unpacked)
Retrieving: python38-docker-pycreds-0.4.0-1.14.noarch.rpm ........................................................[done]
Retrieving package python38-docopt-0.6.2-7.15.noarch (6/23), 37.1 KiB (111.9 KiB unpacked)
Retrieving: python38-docopt-0.6.2-7.15.noarch.rpm ................................................................[done]
Retrieving package python38-fluidity-sm-0.2.0-1.15.noarch (7/23), 18.8 KiB ( 34.0 KiB unpacked)
Retrieving: python38-fluidity-sm-0.2.0-1.15.noarch.rpm ...........................................................[done]
Retrieving package python38-gssapi-1.7.3-1.3.x86_64 (8/23), 508.5 KiB ( 2.2 MiB unpacked)
Retrieving: python38-gssapi-1.7.3-1.3.x86_64.rpm .....................................................[done (1.2 MiB/s)]
Retrieving package python38-importlib-resources-5.4.0-1.4.noarch (9/23), 67.9 KiB (199.2 KiB unpacked)
Retrieving: python38-importlib-resources-5.4.0-1.4.noarch.rpm ....................................................[done]
Retrieving package python38-lexicon-2.0.1-3.2.noarch (10/23), 19.0 KiB ( 24.3 KiB unpacked)
Retrieving: python38-lexicon-2.0.1-3.2.noarch.rpm ................................................................[done]
Retrieving package python38-ptyprocess-0.7.0-1.12.noarch (11/23), 30.9 KiB ( 89.1 KiB unpacked)
Retrieving: python38-ptyprocess-0.7.0-1.12.noarch.rpm ............................................................[done]
Retrieving package python38-pyrsistent-0.18.1-1.2.x86_64 (12/23), 112.9 KiB (497.3 KiB unpacked)
Retrieving: python38-pyrsistent-0.18.1-1.2.x86_64.rpm ............................................................[done]
Retrieving package python38-websocket-client-1.3.2-1.1.noarch (13/23), 112.4 KiB (427.3 KiB unpacked)
Retrieving: python38-websocket-client-1.3.2-1.1.noarch.rpm .......................................................[done]
Retrieving package docker-20.10.14_ce-2.2.x86_64 (14/23), 29.5 MiB (131.7 MiB unpacked)
Retrieving: docker-20.10.14_ce-2.2.x86_64.rpm ........................................................[done (4.8 MiB/s)]
Retrieving package python38-python-dotenv-0.20.0-1.1.noarch (15/23), 40.5 KiB (102.8 KiB unpacked)
Retrieving: python38-python-dotenv-0.20.0-1.1.noarch.rpm .........................................................[done]
Retrieving package python38-pexpect-4.8.0-3.6.noarch (16/23), 145.0 KiB (643.3 KiB unpacked)
Retrieving: python38-pexpect-4.8.0-3.6.noarch.rpm ................................................................[done]
Retrieving package python38-jsonschema-4.4.0-1.3.noarch (17/23), 78.9 KiB (264.5 KiB unpacked)
Retrieving: python38-jsonschema-4.4.0-1.3.noarch.rpm .............................................................[done]
Retrieving package docker-bash-completion-20.10.14_ce-2.2.noarch (18/23), 40.5 KiB (113.6 KiB unpacked)
Retrieving: docker-bash-completion-20.10.14_ce-2.2.noarch.rpm ....................................................[done]
Retrieving package python38-invoke-1.7.0-1.1.noarch (19/23), 161.9 KiB (768.1 KiB unpacked)
Retrieving: python38-invoke-1.7.0-1.1.noarch.rpm .................................................................[done]
Retrieving package python38-paramiko-2.10.4-1.1.noarch (20/23), 327.0 KiB ( 1.8 MiB unpacked)
Retrieving: python38-paramiko-2.10.4-1.1.noarch.rpm ..............................................................[done]
Retrieving package python38-docker-5.0.3-2.2.noarch (21/23), 226.5 KiB ( 1.3 MiB unpacked)
Retrieving: python38-docker-5.0.3-2.2.noarch.rpm .................................................................[done]
Retrieving package python38-dockerpty-0.4.1-4.14.noarch (22/23), 31.3 KiB ( 98.3 KiB unpacked)
Retrieving: python38-dockerpty-0.4.1-4.14.noarch.rpm .............................................................[done]
Retrieving package python38-docker-compose-1.28.5-1.8.noarch (23/23), 256.1 KiB ( 1.1 MiB unpacked)
Retrieving: python38-docker-compose-1.28.5-1.8.noarch.rpm ........................................................[done]
Checking for file conflicts: .....................................................................................[done]
( 1/23) Installing: containerd-1.5.11-1.2.x86_64 .................................................................[done]
( 2/23) Installing: python38-PyNaCl-1.5.0-1.2.x86_64 .............................................................[done]
( 3/23) Installing: python38-PyYAML-6.0-2.3.x86_64 ...............................................................[done]
( 4/23) Installing: python38-click-8.0.4-1.3.noarch ..............................................................[done]
( 5/23) Installing: python38-docker-pycreds-0.4.0-1.14.noarch ....................................................[done]
( 6/23) Installing: python38-docopt-0.6.2-7.15.noarch ............................................................[done]
( 7/23) Installing: python38-fluidity-sm-0.2.0-1.15.noarch .......................................................[done]
( 8/23) Installing: python38-gssapi-1.7.3-1.3.x86_64 .............................................................[done]
( 9/23) Installing: python38-importlib-resources-5.4.0-1.4.noarch ................................................[done]
(10/23) Installing: python38-lexicon-2.0.1-3.2.noarch ............................................................[done]
(11/23) Installing: python38-ptyprocess-0.7.0-1.12.noarch ........................................................[done]
(12/23) Installing: python38-pyrsistent-0.18.1-1.2.x86_64 ........................................................[done]
(13/23) Installing: python38-websocket-client-1.3.2-1.1.noarch ...................................................[done]
Updating /etc/sysconfig/docker ...
(14/23) Installing: docker-20.10.14_ce-2.2.x86_64 ................................................................[done]
(15/23) Installing: python38-python-dotenv-0.20.0-1.1.noarch .....................................................[done]
(16/23) Installing: python38-pexpect-4.8.0-3.6.noarch ............................................................[done]
(17/23) Installing: python38-jsonschema-4.4.0-1.3.noarch .........................................................[done]
(18/23) Installing: docker-bash-completion-20.10.14_ce-2.2.noarch ................................................[done]
(19/23) Installing: python38-invoke-1.7.0-1.1.noarch .............................................................[done]
(20/23) Installing: python38-paramiko-2.10.4-1.1.noarch ..........................................................[done]
(21/23) Installing: python38-docker-5.0.3-2.2.noarch .............................................................[done]
(22/23) Installing: python38-dockerpty-0.4.1-4.14.noarch .........................................................[done]
(23/23) Installing: python38-docker-compose-1.28.5-1.8.noarch ....................................................[done]
locutus@localhost:~> sudo systemctl enable docker
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /usr/lib/systemd/system/docker.service.
locutus@localhost:~> sudo usermod -G docker -a $USER
locutus@localhost:~> sudo systemctl restart docker
locutus@localhost:~> docker version
Client:
Version: 20.10.14-ce
API version: 1.41
Go version: go1.16.15
Git commit: 87a90dc786bd
Built: Fri Apr 29 00:00:00 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2
Fvar%2Frun%2Fdocker.sock/v1.24/version": dial unix /var/run/docker.sock: connect: permission denied
locutus@localhost:~> docker run --rm hello-world
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "
http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
locutus@localhost:~> sudo docker run --rm hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
2db29710123e: Pull complete
Digest: sha256:80f31da1ac7b312ba29d65080fddf797dd76acfb870e677f390d5acba9741b17
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/get-started/
locutus@localhost:~> docker run -d -p 80:80 docker/getting-started
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "
http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
locutus@localhost:~> sudo docker run -dp 80:80 docker/getting-started
Unable to find image 'docker/getting-started:latest' locally
latest: Pulling from docker/getting-started
df9b9388f04a: Pull complete
5867cba5fcbd: Pull complete
4b639e65cb3b: Pull complete
061ed9e2b976: Pull complete
bc19f3e8eeb1: Pull complete
4071be97c256: Pull complete
79b586f1a54b: Pull complete
0c9732f525d6: Pull complete
Digest: sha256:b558be874169471bd4e65bd6eac8c303b271a7ee8553ba47481b73b2bf597aae
Status: Downloaded newer image for docker/getting-started:latest
93d3eb19c18b71cc638d04da735b1f6116c5816dc352965120aa07bdd664e503
locutus@localhost:~>
Hi
See https://jellyfin.org/docs/general/administration/installing.html I would look at podman rather than docker…
I just ran the tarball version, works fine. You could deploy into /usr/local and create a systemd service for it? If running with systemd I would create a jellyfin user with no login to run, and harden the service as well.
If those kind of hoops are what I can expect installing apps like jellyfin, sonarr, radarr, jackett, and others I can’t say Tumbleweed is worth the hassle. By rights I should be able to install all of them via YaST or a straight up install using zypper and simply do a sudo systemctl start and sudo systemctl enable for each of them. I shouldn’t have to be messing with docker, podman, flatpak, snap for any of them.
Locutus64:
If those kind of hoops are what I can expect installing apps like jellyfin, sonarr, radarr, jackett, and others I can’t say Tumbleweed is worth the hassle. By rights I should be able to install all of them via YaST or a straight up install using zypper and simply do a sudo systemctl start and sudo systemctl enable for each of them. I shouldn’t have to be messing with docker, podman, flatpak, snap for any of them.
Hi
Unless it is packaged up and submitted by a contributor for Tumbleweed, then you will be playing a waiting game… openSUSE is a do-ocrity, as in folks package up and submit/maintain.
osc se jellyfin
No matches found for 'jellyfin' in projects
####################################################################
matches for 'jellyfin' in packages:
# Project # Package
home:luc14n0:Jellyfin jellyfin
home:pandom79 jellyfin
home:pmdpalma:Fedora:bucket jellyfin
osc se sonarr
####################################################################
matches for 'sonarr' in projects:
# Project
home:DaAwesomeP:sonarr
####################################################################
matches for 'sonarr' in packages:
# Project # Package
home:DaAwesomeP:sonarr sonarr
home:alarrosa:branches:network sonarr
home:alarrosa:packages sonarr
home:briaguya sonarr
home:junknot sonarr
osc se radarr
No matches found for 'radarr' in projects
No matches found for 'radarr' in packages
osc se jackett
No matches found for 'jackett' in projects
No matches found for 'jackett' in packages
For as long as Opensuse / Opensuse Tumbleweed have been around there really is no excuse for any program not to be available for it. I know I can user Docker but that’s a unnecessary layer that is a pain in the ass to get going properly. I really thought when everyone called Tumbleweed cutting edge that it would have at least as good of a available software base as Arch, but that doesn’t even remotely seem to be the case.
Locutus64:
For as long as Opensuse / Opensuse Tumbleweed have been around there really is no excuse for any program not to be available for it. I know I can user Docker but that’s a unnecessary layer that is a pain in the ass to get going properly. I really thought when everyone called Tumbleweed cutting edge that it would have at least as good of a available software base as Arch, but that doesn’t even remotely seem to be the case.
Hi
That isn’t how the openSUSE project works, people with like needs would look to package up and if they feel comfortable maintaining in the distribution push to a development project and then to Factory for inclusion.
The jellyfin source code is available to compile on your machine. See: https://jellyfin.org/docs/general/administration/building.html
I do that and try to avoid intermediary apps like docker. The compiling is sometimes a challenge but it is fun to figure it out and an accomplishment when successful.
tom kosvic
It’s always been my experience (so far) that one needs to do:
systemctl start service
before doing:
systemctl enable service
I concluded over the years that if there isn’t a service file (which “start” initiates), it won’t/can’t be enabled.
But that’s just my two-cents worth.
As well, maybe becoming root
su -
instead of using
sudo
might help (I’m not fully sure about that, though). Worth a try (it’s free).