Failed to create task for container

Having any issues installing YAMS? This is the place to ask!
Post Reply
1000_Sparrows
Posts: 7
Joined: Thu Sep 26, 2024 10:00 pm
United States of America

Failed to create task for container

Post by 1000_Sparrows »

I am running through the script, but am getting caught on this. Tried checking permissions with docker, but things seem ok there.

====================================================


___ / /\ //\ / /\
/
/| / /::\ | |::\ / /:/_
| |:| / /:/\:\ | |:|:\ / /:/ /\
| |:| / /:/~/::\ ||:|\:\ / /:/ /::\
||:| //:/ /:/\:\ //::::| \:\ //:/ /:/\:\
/
/::::\ \ \:\/:/\/ \ \:\~\_\/ \ \:\/:/~/:/
\~\:\ \ \::/ \ \:\ \ \::/ /:/
\ \:\ \ \:\ \ \:\ \_
\/ /:/
\_\/ \ \:\ \ \:\ /
/:/

\__\/ \_\/ \_\/


Welcome to YAMS (Yet Another Media Server)
Installation process should be really quick
We just need you to answer some questions
We are going to ask for your sudo password in the end

To finish the installation of the CLI



Checking prerequisites...
docker exists ✅
docker compose exists ✅
Where do you want to install the docker-compose file? [/opt/yams]:
What's the user that is going to own the media server files? [yams]:
Please, input your media directory [/srv/media]:
Are you sure your media directory is "/srv/media"? [y/N]: y



Time to choose your media service.
Your media service is responsible for serving your files to your network.
By default, YAMS supports 3 media services:

  • jellyfin (recommended, easier)
  • emby
  • plex (advanced, always online)
    Choose your media service [jellyfin]:

YAMS is going to install "jellyfin" on port "8096"

Time to set up the VPN.
You can check the supported VPN list here: https://yams.media/advanced/vpn.
Do you want to configure a VPN? [Y/n]: Y
Configuring the docker-compose file for the user "yams" on "/opt/yams"...

Copying docker-compose.example.yaml to /opt/yams/docker-compose.yaml...
docker-compose.example.yaml was copied successfuly! ✅

Copying .env.example to /opt/yams/.env...
.env.example was copied successfuly! ✅

Copying docker-compose.custom.yaml to /opt/yams/docker-compose.custom.yaml...
docker-compose.custom.yaml was copied successfuly! ✅
Everything installed correctly! 🎉
Running the server...
This is going to take a while...
WARN[0000] /opt/yams/docker-compose.yaml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 0/11
⠇ Container gluetun Starting 0.8s
⠇ Container radarr Starting 0.8s
⠇ Container lidarr Starting 0.8s
⠇ Container readarr Starting 0.8s
⠇ Container bazarr Starting 0.8s
⠇ Container prowlarr Starting 0.8s
⠇ Container watchtower Starting 0.8s
⠇ Container sonarr Starting 0.8s
⠇ Container portainer Starting 0.8s
⠇ Container jellyfin Starting 0.8s
⠇ Container qbittorrent Starting 0.8s
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "proc" to rootfs at "/proc": mount proc:/proc (via /proc/self/fd/6), flags: 0xe: permission denied: unknown

User avatar
rogs
Site Admin
Posts: 158
Joined: Mon Oct 23, 2023 12:53 pm
Location: Montevideo, Uruguay
Gender:
Contact:
Uruguay

Re: Failed to create task for container

Post by rogs »

Hey @1000_Sparrows!

You are running YAMS in an unprivileged LXC. Try running YAMS in a VM or add privileges to your LXC.

Cheers!

Roger.

YAMS Creator

E: roger (at) rogs.me. Fuck you, email bots.
W: https://rogs.me
gpg: curl -sL https://rogs.me/rogs.txt | gpg --import
fingerprint: ADDF BCB7 8B86 8D93 FC4E 3224 C7EC E9C6 C36E C2E6


Also, I love cats :mrgreen:

Pirate jet, pirate jet
1000_Sparrows
Posts: 7
Joined: Thu Sep 26, 2024 10:00 pm
United States of America

Re: Failed to create task for container

Post by 1000_Sparrows »

I had tried to do that at various times in previous attempts. This go around, I did all of the tasks needed for having those privileges before starting it for the first time. It seemed to not get caught up on anything. This was what my final /etc/pve/lxc/<container id>.conf file looked like:

Code: Select all

  GNU nano 7.2                    /etc/pve/lxc/105.conf                              
# lxc.apparmor.profile%3A unconfined
arch: amd64
cores: 8
features: nesting=1,mknod=1
hostname: yams-lxc
memory: 8192
net0: name=eth0,bridge=vmbr0,firewall=1,gw=10.0.0.1,hwaddr=BC:24:11:4A:88:8E,ip=10.0>
ostype: ubuntu
rootfs: local-lvm:vm-105-disk-0,size=300G
swap: 4096
unprivileged: 0
lxc.cgroup.devices.allow: a
lxc.cap.drop:
lxc.cgroup.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dir

Thanks for your help!

Post Reply