Description of problem: docker container doesn't start Version-Release number of selected component (if applicable): aufs-tools 4.14 0.git2017091> x86_64 cgroup 0.41 2.mga7 x86_64 docker 18.09.0 1.mga7 x86_64 docker-containerd 1.2.0 0.beta.2.2.m> x86_64 glibc-devel 2.29 3.mga7 x86_64 kernel-userspace-headers 5.0.0 1.mga7 x86_64 lib64cgroup1 0.41 2.mga7 x86_64 lib64lxc1 2.0.9 5.mga7 x86_64 lib64xcrypt-devel 4.4.3 1.mga7 x86_64 lxc 2.0.9 5.mga7 x86_64 opencontainers-runc 1.0.0 0.rc6.3.mga7 x86_64 How reproducible: everytime docker-compose up with a yml file for example redmine and postgres Steps to Reproduce: 1. install a fresh docker environment ( urpmi docker ) with all dependencies 2. start docker daemon ( systemctl start docker ) 3. go to the path with your yml file 4. fire up docker-compose up Output: ------------------------------------------------------------ Creating network "docker_redmine" with driver "bridge" Creating volume "docker_redmine-data" with default driver Creating volume "docker_postgres-data" with default driver Pulling redmine (redmine:latest)... latest: Pulling from library/redmine f7e2b70d04ae: Pull complete fd31ea8be251: Pull complete e647615011bb: Pull complete 6609ef3f5c4f: Pull complete a31cda9ce4f0: Pull complete 15608438a3d6: Pull complete e5e7b1d255a3: Pull complete 90c94da70476: Pull complete e2b3e8b0349b: Pull complete 55d404c43a93: Pull complete 9fe72a56503a: Pull complete 4bf86bae1575: Pull complete 0d43069323f5: Pull complete Pulling postgres (postgres:latest)... latest: Pulling from library/postgres f7e2b70d04ae: Already exists 027ad848ac9c: Pull complete 7c040ef66643: Pull complete b891079ad2eb: Pull complete cb64a97e42d9: Pull complete 1b88625f7d89: Pull complete a6ac0b663e77: Pull complete 594497f0a694: Pull complete ca7201b6a21f: Pull complete 48cdfad3f2fd: Pull complete 912fb62e7390: Pull complete 1e6365c64609: Pull complete eda829b73ec7: Pull complete 1dafb86732d6: Pull complete Creating docker_postgres_1 ... Creating docker_redmine_1 ... Pulling postgres (postgres:latest)... Creating docker_redmine_1 ... error Creating docker_postgres_1 ... error ERROR: for docker_redmine_1 Cannot start service redmine: unable to find "net_prio" in controller set: unknown ERROR: for docker_postgres_1 Cannot start service postgres: unable to find "net_prio" in controller set: unknown ERROR: for redmine Cannot start service redmine: unable to find "net_prio" in controller set: unknown ERROR: for postgres Cannot start service postgres: unable to find "net_prio" in controller set: unknown ERROR: Encountered errors while bringing up the project. ------------------------------------------------------------------- And the content of the yml file: ---------------------------------------------------------------- version: '3.1' services: postgres: image: postgres:latest restart: always networks: - redmine volumes: - postgres-data:/var/lib/postgresql/data environment: - 'POSTGRES_PASSWORD=redmine' - 'POSTGRES_DB=redmine' redmine: image: redmine:latest restart: always networks: - redmine volumes: - redmine-data:/usr/src/redmine/files ports: - 80:3000 environment: - 'REDMINE_DB_POSTGRES=postgres' - 'REDMINE_DB_DATABASE=redmine' - 'REDMINE_DB_PASSWORD=redmine' - 'SMTP_ENABLED=false' - 'SMTP_METHOD=smtp' - 'SMTP_DOMAIN=example.com' - 'SMTP_HOST=192.168.1.254' - 'SMTP_PORT=25' - 'SMTP_STARTTLS=true' volumes: postgres-data: redmine-data: networks: redmine: driver: bridge -------------------------------------------------------------
Assigning to our registered docker maintainer.
Assignee: bugsquad => brunoCC: (none) => marja11
Seems linked to the version of systemd. See https://github.com/docker/for-linux/issues/545 A new containerd 1.2.5 seems to have a fix for that. Updating as we speak. Will let you know when you can try.
Status: NEW => ASSIGNED
Just pushed docker-containerd-1.2.5 to cauldron. Please update and tell us if that fixes your issue.
works again with docker-containerd-1.2.5-1.mga7 docker-18.09.3-2.mga7 thank you good work. I think you can close this bug.
Solved per user feedback
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED