[GH-ISSUE #330] Outdated Mesa in GOW images fails to run with newer HW

bsakaguchi commented

2026-10-15 12:58:30 +00:00

Owner

Originally created by @popsUlfr on GitHub (Jan 5, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/330

Hello,

I've deployed this project with rootful podman on an AMD RYZEN AI MAX+ 395 w/ Radeon 8060S, it works but while streaming the logs are constantly spammed with:

SIVPE ERROR ../src/gallium/drivers/radeonsi/si_vpe.c:947 si_vpe_construct_blt Failed in checking process operation and build settings(9)

Any idea what could be wrong here ?

Originally created by @popsUlfr on GitHub (Jan 5, 2026). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/330 Hello, I've deployed this project with rootful podman on an AMD RYZEN AI MAX+ 395 w/ Radeon 8060S, it works but while streaming the logs are constantly spammed with: ``` SIVPE ERROR ../src/gallium/drivers/radeonsi/si_vpe.c:947 si_vpe_construct_blt Failed in checking process operation and build settings(9) ``` Any idea what could be wrong here ?

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@ABeltramo commented on GitHub (Jan 5, 2026):

I suppose it's the outdated Mesa version baked in our Docker images (Ubuntu based). I'm going to try making a new set of images based on something a bit more cutting edge like Fedora; stay tuned 😉

@ABeltramo commented on GitHub (Jan 5, 2026): I suppose it's the outdated Mesa version baked in our Docker images (Ubuntu based). I'm going to try making a new set of images based on something a bit more cutting edge like Fedora; stay tuned 😉

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@ABeltramo commented on GitHub (Jan 7, 2026):

Can you try out the image that I've just pushed in https://github.com/games-on-whales/gow/pull/282 ? It's still WIP, there might be other things broken given that it's a complete distro change; any feedback is welcome 😉

@ABeltramo commented on GitHub (Jan 7, 2026): Can you try out the image that I've just pushed in https://github.com/games-on-whales/gow/pull/282 ? It's still WIP, there might be other things broken given that it's a complete distro change; any feedback is welcome 😉

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@popsUlfr commented on GitHub (Jan 8, 2026):

I suppose it's the outdated Mesa version baked in our Docker images (Ubuntu based). I'm going to try making a new set of images based on something a bit more cutting edge like Fedora; stay tuned 😉

Cool, thanks!

Can you try out the image that I've just pushed in games-on-whales/gow#282 ? It's still WIP, there might be other things broken given that it's a complete distro change; any feedback is welcome 😉

Does the linked PR also concern the Wolf UI ? I'm getting the log spam as soon as I stream the Wolf Interface. And I'm not really sure how to properly test the new images or build them, this is all a bit over my head right now.

@popsUlfr commented on GitHub (Jan 8, 2026): > I suppose it's the outdated Mesa version baked in our Docker images (Ubuntu based). I'm going to try making a new set of images based on something a bit more cutting edge like Fedora; stay tuned 😉 Cool, thanks! > Can you try out the image that I've just pushed in [games-on-whales/gow#282](https://github.com/games-on-whales/gow/pull/282) ? It's still WIP, there might be other things broken given that it's a complete distro change; any feedback is welcome 😉 Does the linked PR also concern the Wolf UI ? I'm getting the log spam as soon as I stream the Wolf Interface. And I'm not really sure how to properly test the new images or build them, this is all a bit over my head right now.

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@ABeltramo commented on GitHub (Jan 8, 2026):

No worries, I was just eager to get that tested but in your case you'll have to wait until Wolf is re-built on top of that Fedora image. Sorry for the confusion!

I'll ping you once it's all done and dusted!

@ABeltramo commented on GitHub (Jan 8, 2026): No worries, I was just eager to get that tested but in your case you'll have to wait until Wolf is re-built on top of that Fedora image. Sorry for the confusion! I'll ping you once it's all done and dusted!

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@popsUlfr commented on GitHub (Jan 8, 2026):

No worries, I was just eager to get that tested but in your case you'll have to wait until Wolf is re-built on top of that Fedora image. Sorry for the confusion!

I'll ping you once it's all done and dusted!

Ok, thanks for confirming. I wasn't sure if I missed a wip wolf-ui image or not.

While on the topic of log spam, there's also this coming up constantly in the logs:

Jan 08 12:50:43 fwd podman[164457]: @ - - [08/Jan/2026:12:50:43 +0100] "GET /v1.41/containers/feeece1cb5fcf29dc14ec9780bab9e9e5289969d344fc69fa0cf86123b7731f4/json HTTP/1.1" 200 9681 "" ""

This is wolf checking on the image states right ? Does it need to do it so often ? Just asking if it's as intended.

@popsUlfr commented on GitHub (Jan 8, 2026): > No worries, I was just eager to get that tested but in your case you'll have to wait until Wolf is re-built on top of that Fedora image. Sorry for the confusion! > > I'll ping you once it's all done and dusted! Ok, thanks for confirming. I wasn't sure if I missed a wip wolf-ui image or not. While on the topic of log spam, there's also this coming up constantly in the logs: ``` Jan 08 12:50:43 fwd podman[164457]: @ - - [08/Jan/2026:12:50:43 +0100] "GET /v1.41/containers/feeece1cb5fcf29dc14ec9780bab9e9e5289969d344fc69fa0cf86123b7731f4/json HTTP/1.1" 200 9681 "" "" ``` This is wolf checking on the image states right ? Does it need to do it so often ? Just asking if it's as intended.

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@PenTurDucKenLinE commented on GitHub (Jan 16, 2026):

@ABeltramo I'm also having the same issue that @popsUlfr mentioned, with similar hardware, albeit likely different software. I'm running GOW on Unraid OS on a system with AMD RYZEN AI MAX+ 395 w/ Radeon 8060S. The container log is flooded with the following:
"SIVPE ERROR ../src/gallium/drivers/radeonsi/si_vpe.c:947 si_vpe_construct_blt Failed in checking process operation and build settings(9)"

I can successfully use Moonlight to connect to Wolf UI, enter the Steam container, and engage with Steam. However, any time I try to start any game (simple or complex), the game fails to launch without even creating a window. One of the steam logs notes the following
==> /home/retro/.steam/steam/logs/webhelper-linux.txt <== [2026-01-16 04:28:06] [821:874:0116/042806.982148:ERROR:ffmpeg_common.cc(959)] Unsupported pixel format: -1

I'm not sure if the errors are related or not.

@PenTurDucKenLinE commented on GitHub (Jan 16, 2026): @ABeltramo I'm also having the same issue that @popsUlfr mentioned, with similar hardware, albeit likely different software. I'm running GOW on Unraid OS on a system with AMD RYZEN AI MAX+ 395 w/ Radeon 8060S. The container log is flooded with the following: "SIVPE ERROR ../src/gallium/drivers/radeonsi/si_vpe.c:947 si_vpe_construct_blt Failed in checking process operation and build settings(9)" I can successfully use Moonlight to connect to Wolf UI, enter the Steam container, and engage with Steam. However, any time I try to start any game (simple or complex), the game fails to launch without even creating a window. One of the steam logs notes the following ==> /home/retro/.steam/steam/logs/webhelper-linux.txt <== [2026-01-16 04:28:06] [821:874:0116/042806.982148:ERROR:ffmpeg_common.cc(959)] Unsupported pixel format: -1 I'm not sure if the errors are related or not.

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@PenTurDucKenLinE commented on GitHub (Jan 20, 2026):

@ABeltramo I've tinkered a bit with your fedora-based image, and I can actually get Steam running now and play some "basic" games (like VVVVVV or The Messenger).

@PenTurDucKenLinE commented on GitHub (Jan 20, 2026): @ABeltramo I've tinkered a bit with your fedora-based image, and I can actually get Steam running now and play some "basic" games (like VVVVVV or The Messenger).

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@tomthepeach commented on GitHub (Jan 27, 2026):

@PenTurDucKenLinE Could you share what you tinkered?

@tomthepeach commented on GitHub (Jan 27, 2026): @PenTurDucKenLinE Could you share what you tinkered?

bsakaguchi commented

2026-10-15 12:58:31 +00:00

Author

Owner

@PenTurDucKenLinE commented on GitHub (Jan 29, 2026):

First, I'm a novice coder... very, very, VERY NOVICE. I took a couple programming classes many moons ago and require an AI crutch to do anything useful... So take all this with a grain of salt!

I think the main issues I had where were (1) differing references to Steam install location; (2) AMD-specific packages/references missing; and (3) host-OS specific shenanigans. So, here are some of the main things I tinkered:

1.) In steam.sh (apps/steam/build/scripts), changed this

STEAMDIR="${$HOME/.local/share}/Steam"
echo "Steam directory: $STEAMDIR"

if [[ ! -f "$STEAMDIR/steam.sh" ]]; then
    mkdir -p "$STEAMDIR"
    cd "$STEAMDIR"
    tar xJf /usr/lib/steam/bootstraplinux_ubuntu12_32.tar.xz
    mkdir -p ~/.steam
    ln -fns "$STEAMDIR" ~/.steam/steam
fi

to

STEAMDIR="${HOME}/.local/share/Steam"
STEAMDIR_LEGACY="${HOME}/.steam/steam"
echo "Steam directory: $STEAMDIR"

if [[ ! -f "$STEAMDIR/steam.sh" ]]; then
    mkdir -p "$STEAMDIR"
    cd "$STEAMDIR"
    tar xJf /usr/lib/steam/bootstraplinux_ubuntu12_32.tar.xz
    mkdir -p "$STEAMDIR_LEGACY"
    ln -fns "$STEAMDIR" "$STEAMDIR_LEGACY"
fi

2.) In system-services.sh, changed this

  mkdir -p "$HOME/.steam/steam/"
  mkdir -p "$HOME/.steam/debian-installation/"
  touch "$HOME/.steam/debian-installation/.cef-enable-remote-debugging"

to

  mkdir -p "$STEAMDIR"
  mkdir -p "$STEAMDIR/debian-installation"
  touch "$STEAMDIR/debian-installation/.cef-enable-remote-debugging"

and added the following:

STEAMDIR="${HOME}/.local/share/Steam"
STEAMDIR_LEGACY="${HOME}/.steam/steam"
echo "Steam directory: $STEAMDIR"

3.) In steamos-dbus-watchdog.sh, changed this:

function shutdown_steam() {
    gow_log "[steamos-dbus-watchdog] Shutting down Steam..."
    steam -shutdown
    exit 0
}

to

function shutdown_steam() {
    gow_log "[steamos-dbus-watchdog] Shutting down Steam..."
    "$HOME/.local/share/Steam/steam.sh" -shutdown
 -shutdown
    exit 0
}

4.) In startup.sh, changed this:

# Recursively creating Steam necessary folders (https://github.com/ValveSoftware/steam-for-linux/issues/6492)
mkdir -p "$HOME/.steam/ubuntu12_32/steam-runtime"

to

# Recursively creating Steam necessary folders (https://github.com/ValveSoftware/steam-for-linux/issues/6492)
mkdir -p "$HOME/.local/share/Steam/ubuntu12_32/steam-runtime"
export WINEPREFIX="$HOME/.local/share/WolfSteam/pfx"
export STEAM_COMPAT_DATA_PATH="$WINEPREFIX"

5.) I also tried to add a variety of AMD-specific packages or arguments to the base-app image and wolf.config.toml.

@PenTurDucKenLinE commented on GitHub (Jan 29, 2026): First, I'm a novice coder... very, very, VERY NOVICE. I took a couple programming classes many moons ago and require an AI crutch to do anything useful... So take all this with a grain of salt! I think the main issues I had where were (1) differing references to Steam install location; (2) AMD-specific packages/references missing; and (3) host-OS specific shenanigans. So, here are some of the main things I tinkered: **_1.) In steam.sh (apps/steam/build/scripts), changed this_** ``` STEAMDIR="${$HOME/.local/share}/Steam" echo "Steam directory: $STEAMDIR" if [[ ! -f "$STEAMDIR/steam.sh" ]]; then mkdir -p "$STEAMDIR" cd "$STEAMDIR" tar xJf /usr/lib/steam/bootstraplinux_ubuntu12_32.tar.xz mkdir -p ~/.steam ln -fns "$STEAMDIR" ~/.steam/steam fi ``` to ``` STEAMDIR="${HOME}/.local/share/Steam" STEAMDIR_LEGACY="${HOME}/.steam/steam" echo "Steam directory: $STEAMDIR" if [[ ! -f "$STEAMDIR/steam.sh" ]]; then mkdir -p "$STEAMDIR" cd "$STEAMDIR" tar xJf /usr/lib/steam/bootstraplinux_ubuntu12_32.tar.xz mkdir -p "$STEAMDIR_LEGACY" ln -fns "$STEAMDIR" "$STEAMDIR_LEGACY" fi ``` **_2.) In system-services.sh, changed this_** ``` mkdir -p "$HOME/.steam/steam/" mkdir -p "$HOME/.steam/debian-installation/" touch "$HOME/.steam/debian-installation/.cef-enable-remote-debugging" ``` to ``` mkdir -p "$STEAMDIR" mkdir -p "$STEAMDIR/debian-installation" touch "$STEAMDIR/debian-installation/.cef-enable-remote-debugging" ``` and added the following: ``` STEAMDIR="${HOME}/.local/share/Steam" STEAMDIR_LEGACY="${HOME}/.steam/steam" echo "Steam directory: $STEAMDIR" ``` **_3.) In steamos-dbus-watchdog.sh, changed this:_** ``` function shutdown_steam() { gow_log "[steamos-dbus-watchdog] Shutting down Steam..." steam -shutdown exit 0 } ``` to ``` function shutdown_steam() { gow_log "[steamos-dbus-watchdog] Shutting down Steam..." "$HOME/.local/share/Steam/steam.sh" -shutdown -shutdown exit 0 } ``` **_4.) In startup.sh, changed this:_** ``` # Recursively creating Steam necessary folders (https://github.com/ValveSoftware/steam-for-linux/issues/6492) mkdir -p "$HOME/.steam/ubuntu12_32/steam-runtime" ``` to ``` # Recursively creating Steam necessary folders (https://github.com/ValveSoftware/steam-for-linux/issues/6492) mkdir -p "$HOME/.local/share/Steam/ubuntu12_32/steam-runtime" export WINEPREFIX="$HOME/.local/share/WolfSteam/pfx" export STEAM_COMPAT_DATA_PATH="$WINEPREFIX" ``` **_5.) I also tried to add a variety of AMD-specific packages or arguments to the base-app image and wolf.config.toml._**

bsakaguchi commented

2026-10-15 12:58:32 +00:00

Author

Owner

@ABeltramo commented on GitHub (Jan 29, 2026):

Thanks @PenTurDucKenLinE for sharing.
I've tested your changes locally, and it seems to work properly now with the paths, so I went ahead and pushed them in the PR.

I also tried to add a variety of AMD-specific packages or arguments to the base-app image and wolf.config.toml.

What was missing in your setup?

@ABeltramo commented on GitHub (Jan 29, 2026): Thanks @PenTurDucKenLinE for sharing. I've tested your changes locally, and it seems to work properly now with the paths, so I went ahead and pushed them in the PR. > I also tried to add a variety of AMD-specific packages or arguments to the base-app image and wolf.config.toml. What was missing in your setup?

bsakaguchi commented

2026-10-15 12:58:32 +00:00

Author

Owner

@PenTurDucKenLinE commented on GitHub (Jan 29, 2026):

Wow, that's great! Thank you @ABeltramo ! Glad I could contribute! :-)

Regarding the other changes I made, here's are two caveats:
(1) I'm trying to run GOW on Unraid, which as you know has some things a bit different than other modern OS's (e.g., user management, file permissions management, and access to hardware stacks). So, I've been trying to figure out what are Unraid-specific quirks I need to account for, what are AMD-specific quirks, and finally game-specific quirks. (For example, I can some 3D games, but I can't run Black Mesa, which is not correctly monitoring my AMD system's ability to expand VRAM)
(2) I'm a novice at this stuff, so my "methodology" might be introducing unnecessary changes as I hunt for the actual quirks. I use AI to find and recommend specific changes based on error messages and observations, while I try to personally monitor the broader logic of what's being recommended. Even with my novice brain, I still find mistakes in what AI recommends.

With that in mind, here are some other changes I made:

In the base-app Dockerfile, changed this:

          ARG REQUIRED_PACKAGES="\
              mesa-dri-drivers mesa-vulkan-drivers mesa-va-drivers mesa-libgbm mesa-libGL mesa-libEGL \
              egl-gbm \
              gamescope sway \
              xorg-x11-server-Xwayland kitty nano \
              waybar default-fonts xdg-desktop-portal xdg-desktop-portal-gtk psmisc \
              mangohud \
              sdl2-compat ncurses \
              dbus-daemon \
              vulkan-loader vulkan-tools vulkan-validation-layers \
              libdecor \
              libva-utils mesa-vdpau-drivers \
          "
          
          RUN dnf install -y $REQUIRED_PACKAGES && \
              dnf clean all

to

          ARG REQUIRED_PACKAGES="\
>>>           mesa-dri-drivers mesa-vulkan-drivers mesa-va-drivers mesa-vdpau-drivers \
              mesa-libgbm mesa-libGL mesa-libEGL \
              egl-gbm \
              gamescope sway \
              xorg-x11-server-Xwayland kitty nano \
              waybar default-fonts xdg-desktop-portal xdg-desktop-portal-gtk psmisc \
              mangohud \
              sdl2-compat ncurses \
              dbus-daemon \
>>>           vulkan-loader vulkan-tools vulkan-validation-layers \
>>>           libdecor \
>>>           ffmpeg \
>>>           libva libva-utils \
          "
          
>>>       RUN dnf install -y \
>>>             https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \
>>>             https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm \
>>>           && dnf -y upgrade --refresh \
>>>           && dnf install -y ${REQUIRED_PACKAGES} \
>>>           && dnf clean all

Maybe I could have added these to the Steam app dockerfile instead?

In "10-setup_user.sh", changed the following:

    gow_log "Ensure XDG_RUNTIME_DIR is writable"
    chown -R "${PUID}:${PGID}" "${XDG_RUNTIME_DIR}"

to

    gow_log "Ensure XDG_RUNTIME_DIR=$XDG_RUNTIME_DIR is writable"
    chown -R "${PUID}:${PGID}" "${XDG_RUNTIME_DIR}"

    gow_log "Ensure XDG_RUNTIME_DIR=/run/user/${PUID} exists and is writable"
    mkdir -p /run/user/${PUID}
    chown ${PUID}:${PGID} /run/user/${PUID}
    chmod 700 /run/user/${PUID}

Made the following changes to the Steam entry in the config.toml:

        "HostConfig": {
          "IpcMode": "host",
          "CapAdd": ["SYS_ADMIN", "SYS_NICE", "SYS_PTRACE", "NET_RAW", "MKNOD", "NET_ADMIN"],
          "SecurityOpt": ["seccomp=unconfined", "apparmor=unconfined"],
          "Ulimits": [{"Name":"nofile", "Hard":10240, "Soft":10240}],
          "Privileged": false,
          "DeviceCgroupRules": ["c 13:* rmw", "c 244:* rmw"],
>>>       "GroupAdd": ["video"]
        }

and

>>>          devices = [ '/dev/dri:/dev/dri', '/dev/kfd:/dev/kfd' ]
>>>          env = [
>>>               'PROTON_LOG=1',
>>>               'RUN_SWAY=true',
>>>               'GOW_REQUIRED_DEVICES=/dev/input/* /dev/dri/* /dev/kfd/*',
>>>               'XAUTHORITY=/tmp/slim.auth',
>>>               'XDG_RUNTIME_DIR=/run/user/1000',
>>>               'RADV_FORCE_VRAM=65536',
>>>               'RADV_FORCE_GTT=65536',
>>>               'RADV_VRAM_OVERRIDE=1'
>>>           ]
              image = 'gow-app-steam:fedora'
>>>           mounts = [
>>>               '/var/run/slim.auth:/tmp/slim.auth:ro',
>>>               '/tmp/.X11-unix:/tmp/.X11-unix:rw'
>>>           ]
              name = 'WolfSteam'
              ports = []
              type = 'docker'

@PenTurDucKenLinE commented on GitHub (Jan 29, 2026): Wow, that's great! Thank you @ABeltramo ! Glad I could contribute! :-) Regarding the other changes I made, here's are two caveats: (1) I'm trying to run GOW on Unraid, which as you know has some things a bit different than other modern OS's (e.g., user management, file permissions management, and access to hardware stacks). So, I've been trying to figure out what are Unraid-specific quirks I need to account for, what are AMD-specific quirks, and finally game-specific quirks. (For example, I can some 3D games, but I can't run Black Mesa, which is not correctly monitoring my AMD system's ability to expand VRAM) (2) I'm a novice at this stuff, so my "methodology" might be introducing unnecessary changes as I hunt for the actual quirks. I use AI to find and recommend specific changes based on error messages and observations, while I try to personally monitor the broader logic of what's being recommended. Even with my novice brain, I still find mistakes in what AI recommends. With that in mind, here are some other changes I made: 1. In the base-app Dockerfile, changed this: ``` ARG REQUIRED_PACKAGES="\ mesa-dri-drivers mesa-vulkan-drivers mesa-va-drivers mesa-libgbm mesa-libGL mesa-libEGL \ egl-gbm \ gamescope sway \ xorg-x11-server-Xwayland kitty nano \ waybar default-fonts xdg-desktop-portal xdg-desktop-portal-gtk psmisc \ mangohud \ sdl2-compat ncurses \ dbus-daemon \ vulkan-loader vulkan-tools vulkan-validation-layers \ libdecor \ libva-utils mesa-vdpau-drivers \ " RUN dnf install -y $REQUIRED_PACKAGES && \ dnf clean all ``` to ``` ARG REQUIRED_PACKAGES="\ >>> mesa-dri-drivers mesa-vulkan-drivers mesa-va-drivers mesa-vdpau-drivers \ mesa-libgbm mesa-libGL mesa-libEGL \ egl-gbm \ gamescope sway \ xorg-x11-server-Xwayland kitty nano \ waybar default-fonts xdg-desktop-portal xdg-desktop-portal-gtk psmisc \ mangohud \ sdl2-compat ncurses \ dbus-daemon \ >>> vulkan-loader vulkan-tools vulkan-validation-layers \ >>> libdecor \ >>> ffmpeg \ >>> libva libva-utils \ " >>> RUN dnf install -y \ >>> https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \ >>> https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm \ >>> && dnf -y upgrade --refresh \ >>> && dnf install -y ${REQUIRED_PACKAGES} \ >>> && dnf clean all ``` Maybe I could have added these to the Steam app dockerfile instead? 2. In "10-setup_user.sh", changed the following: ``` gow_log "Ensure XDG_RUNTIME_DIR is writable" chown -R "${PUID}:${PGID}" "${XDG_RUNTIME_DIR}" ``` to ``` gow_log "Ensure XDG_RUNTIME_DIR=$XDG_RUNTIME_DIR is writable" chown -R "${PUID}:${PGID}" "${XDG_RUNTIME_DIR}" gow_log "Ensure XDG_RUNTIME_DIR=/run/user/${PUID} exists and is writable" mkdir -p /run/user/${PUID} chown ${PUID}:${PGID} /run/user/${PUID} chmod 700 /run/user/${PUID} ``` 3. Made the following changes to the Steam entry in the config.toml: ``` "HostConfig": { "IpcMode": "host", "CapAdd": ["SYS_ADMIN", "SYS_NICE", "SYS_PTRACE", "NET_RAW", "MKNOD", "NET_ADMIN"], "SecurityOpt": ["seccomp=unconfined", "apparmor=unconfined"], "Ulimits": [{"Name":"nofile", "Hard":10240, "Soft":10240}], "Privileged": false, "DeviceCgroupRules": ["c 13:* rmw", "c 244:* rmw"], >>> "GroupAdd": ["video"] } ``` and ``` >>> devices = [ '/dev/dri:/dev/dri', '/dev/kfd:/dev/kfd' ] >>> env = [ >>> 'PROTON_LOG=1', >>> 'RUN_SWAY=true', >>> 'GOW_REQUIRED_DEVICES=/dev/input/* /dev/dri/* /dev/kfd/*', >>> 'XAUTHORITY=/tmp/slim.auth', >>> 'XDG_RUNTIME_DIR=/run/user/1000', >>> 'RADV_FORCE_VRAM=65536', >>> 'RADV_FORCE_GTT=65536', >>> 'RADV_VRAM_OVERRIDE=1' >>> ] image = 'gow-app-steam:fedora' >>> mounts = [ >>> '/var/run/slim.auth:/tmp/slim.auth:ro', >>> '/tmp/.X11-unix:/tmp/.X11-unix:rw' >>> ] name = 'WolfSteam' ports = [] type = 'docker' ```

bsakaguchi commented

2026-10-15 12:58:32 +00:00

Author

Owner

@martonbtoth commented on GitHub (Mar 6, 2026):

I also had problems (support for the BC-250) that was caused by the old mesa version bundled in wolf specifically, which were resolved by updating mesa through a PPA in the image. I'm not sure about the general comfort level regarding this, but this approach would be much less drastic than switching distros.

@martonbtoth commented on GitHub (Mar 6, 2026): I also had problems (support for the BC-250) that was caused by the old mesa version bundled in wolf specifically, which were resolved by updating mesa through a [PPA](https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa) in the image. I'm not sure about the general comfort level regarding this, but this approach would be much less drastic than switching distros.

bsakaguchi commented

2026-10-15 12:58:32 +00:00

Author

Owner

@EnumC commented on GitHub (Jun 25, 2026):

Is there appetite to bump wolf to Ubuntu 26.04 LTS? It landed quite a few bugfixes for newer AMD APUs, including bumping mesa version.

@EnumC commented on GitHub (Jun 25, 2026): Is there appetite to bump wolf to Ubuntu 26.04 LTS? It landed quite a few bugfixes for newer AMD APUs, including bumping mesa version.

bsakaguchi commented

2026-10-15 12:58:32 +00:00

Author

Owner

@ABeltramo commented on GitHub (Jun 25, 2026):

We have a bunch of WIP PRs for moving GOW and Wolf to Fedora, if anyone would like to help testing them on different HW it would be greatly appreciated.

@ABeltramo commented on GitHub (Jun 25, 2026): We have a bunch of WIP PRs for moving GOW and Wolf to Fedora, if anyone would like to help testing them on different HW it would be greatly appreciated.

Rows
Columns

[GH-ISSUE #330] Outdated Mesa in GOW images fails to run with newer HW #230