steam-runtime icon indicating copy to clipboard operation
steam-runtime copied to clipboard

Unable to build with fresh new install of Fedora 31

Open Dimitri2g opened this issue 4 years ago • 4 comments

I did a git clone and have been following the instructions and it seems I am failing to build. Instructions: Instructions

I ran: ./steam-runtime/setup_docker.sh --beta amd64 --extra-bootstrap=./proton/steamrt-bootstrap.sh steam-proton-dev

and at the end I got:

Step 8/20 : RUN 	set -xe; 	if [ -n "${proxy}" ]; then 		echo "configure proxy"; 		echo "export http_proxy=${proxy}" >> /etc/bash.bashrc; 		echo "export https_proxy=${proxy}" >> /etc/bash.bashrc; 		echo "export ftp_proxy=${proxy}" >> /etc/bash.bashrc; 		echo "Acquire::http::proxy \"${proxy}\";" > /etc/apt/apt.conf.d/01proxy; 		echo "Acquire::https::proxy \"${proxy}\";" >> /etc/apt/apt.conf.d/01proxy; 	fi; 	if [ -n "${no_proxy}" ]; then 		echo "export no_proxy=${no_proxy}" >> /etc/bash.bashrc; 		oldIFS="$IFS"; 		IFS=","; 		for nope in ${no_proxy}; do 			case "$nope" in 				(.*) 					;; 				(*) 					echo "Acquire::http::proxy::${nope} \"DIRECT\";" >> /etc/apt/apt.conf.d/01proxy; 		echo "Acquire::https::proxy::${nope} \"DIRECT\";" >> /etc/apt/apt.conf.d/01proxy; 					;; 			esac; 		done; 		IFS="$oldIFS"; 	fi
 ---> Running in e2cfab95578d
OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown

real	0m28.535s
user	0m0.645s
sys	0m0.481s
Script done, file is /tmp/steam-runtime-setup-chroot-Vm8.log
[steam-runtime-setup-chroot-Vm8.log](https://github.com/ValveSoftware/Proton/files/4536111/steam-runtime-setup-chroot-Vm8.log)

Full log attached steam-runtime-setup-chroot-Vm8.log

Dimitri2g avatar Apr 30 '20 17:04 Dimitri2g

setup_docker.sh is deprecated. For the recommended approach, please see: https://github.com/ValveSoftware/steam-runtime#using-docker

However, that won't necessarily solve your problem.

OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown

I would recommend trying a very simple Docker example, for example pulling and running https://hub.docker.com/_/hello-world. If that doesn't work either, report the problem to your distribution (Fedora).

If Fedora is actually using Podman instead of Docker, then running it unprivileged (without sudo) might be better?

smcv avatar May 12 '20 16:05 smcv

@Dimitri2g Yeah, I haven't updated those wiki instructions in a long time… and I don't have time to get over them and fix it myself at the moment.

As for the problem at hand: it's most likely caused by Docker still not understanding cgroups v2, and this API was turned on by default in Fedora 31. There are two ways to fix it:

  • Use podman instead of Docker. It's a Docker fork with issues like these fixed, it's included in Fedora repositories and should work as a drop-in replacement for docker.
  • Force-disable cgroupsv2

Here's an article that seems to cover both options in detail

dreamer avatar May 12 '20 17:05 dreamer

@smcv and @dreamer Thank you both for responding.

I will try to use podman and disable cgroupsv2

Dimitri2g avatar May 13 '20 04:05 Dimitri2g

@Dimitri2g With podman you won't need to disable cgroupsv2.

dreamer avatar May 13 '20 13:05 dreamer