[GH-ISSUE #344] Steam not launching #237

New issue

Open

opened 2026-10-15 12:58:35 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

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

Owner

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

I'm running with an Intel Arc. The GUI launches successfully but when starting Steam, I am kicked back to the GUI. This is the same regardless of Sway or Gamescope.

Wolf is running in a privileged LXC container (on Incus) with Podman.

Incus config is the follow:

architecture: x86_64
config:
  image.architecture: amd64
  image.description: Ubuntu noble amd64 (20260117_07:42)
  image.os: Ubuntu
  image.release: noble
  image.requirements.cgroup: v2
  image.serial: '20260117_07:42'
  image.type: squashfs
  image.variant: default
  raw.lxc: |

    lxc.net.0.type = none
    lxc.cgroup2.devices.allow = a
    lxc.cap.drop =
    lxc.mount.entry = /dev/dri dev/dri none bind,optional,create=dir
    lxc.mount.entry = /run/udev mnt/udev none bind,optional,create=dir
    lxc.mount.entry = /dev mnt/dev none bind,optional,create=dir
    lxc.mount.entry = /dev/fuse dev/fuse none bind,optional,create=file
  security.nesting: 'true'
  security.privileged: 'true'
  volatile.base_image: 8419409732415eb5832a959959576fd9a5d9ec9401c0df6314d383cc419857c9
  volatile.cloud-init.instance-id: ce55da7c-5ec6-4529-9554-c2216d4b4cac
  volatile.eth0.host_name: vethfbe5f03e
  volatile.eth0.hwaddr: 10:66:6a:b7:54:7b
  volatile.idmap.base: '0'
  volatile.idmap.current: '[]'
  volatile.idmap.next: '[]'
  volatile.last_state.idmap: '[]'
  volatile.last_state.power: RUNNING
  volatile.uuid: 34882005-c499-4387-a68f-3656e9ffdca4
  volatile.uuid.generation: 34882005-c499-4387-a68f-3656e9ffdca4
devices:
  root:
    path: /
    pool: local
    type: disk
ephemeral: false
profiles:
  - default
stateful: false
description: ''
created_at: '2026-01-18T10:14:25.387442471Z'
name: wolf
status: Running
status_code: 103
last_used_at: '2026-01-23T18:42:58.822982934Z'
location: none
type: container
project: default

Podman:

[Unit]
Description=Wolf / Games On Whales
Requires=network-online.target podman.socket
After=network-online.target podman.socket

[Service]
TimeoutStartSec=900
ExecStartPre=-/usr/bin/podman rm --force WolfPulseAudio
Restart=on-failure
RestartSec=5
StartLimitBurst=5

[Container]
AutoUpdate=registry
ContainerName=%p
HostName=%p
Image=ghcr.io/games-on-whales/wolf:stable
Network=host
SecurityLabelDisable=true
PodmanArgs=--ipc=host --device-cgroup-rule "c 13:* rmw"
AddDevice=/dev/dri
Volume=/mnt/dev:/dev:rw
Volume=/mnt/udev:/run/udev:rw
Volume=/etc/wolf/:/etc/wolf:z
Volume=/run/podman/podman.sock:/var/run/docker.sock:ro
#Environment=WOLF_STOP_CONTAINER_ON_EXIT=TRUE
Environment=WOLF_LOG_LEVEL=DEBUG

[Install]
WantedBy=multi-user.target

Output logs are attached, any help would be greatly appreciated!

log0.txt
log1.txt

Originally created by @amaccuish on GitHub (Jan 23, 2026). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/344 I'm running with an Intel Arc. The GUI launches successfully but when starting Steam, I am kicked back to the GUI. This is the same regardless of Sway or Gamescope. Wolf is running in a privileged LXC container (on Incus) with Podman. Incus config is the follow: ``` architecture: x86_64 config: image.architecture: amd64 image.description: Ubuntu noble amd64 (20260117_07:42) image.os: Ubuntu image.release: noble image.requirements.cgroup: v2 image.serial: '20260117_07:42' image.type: squashfs image.variant: default raw.lxc: | lxc.net.0.type = none lxc.cgroup2.devices.allow = a lxc.cap.drop = lxc.mount.entry = /dev/dri dev/dri none bind,optional,create=dir lxc.mount.entry = /run/udev mnt/udev none bind,optional,create=dir lxc.mount.entry = /dev mnt/dev none bind,optional,create=dir lxc.mount.entry = /dev/fuse dev/fuse none bind,optional,create=file security.nesting: 'true' security.privileged: 'true' volatile.base_image: 8419409732415eb5832a959959576fd9a5d9ec9401c0df6314d383cc419857c9 volatile.cloud-init.instance-id: ce55da7c-5ec6-4529-9554-c2216d4b4cac volatile.eth0.host_name: vethfbe5f03e volatile.eth0.hwaddr: 10:66:6a:b7:54:7b volatile.idmap.base: '0' volatile.idmap.current: '[]' volatile.idmap.next: '[]' volatile.last_state.idmap: '[]' volatile.last_state.power: RUNNING volatile.uuid: 34882005-c499-4387-a68f-3656e9ffdca4 volatile.uuid.generation: 34882005-c499-4387-a68f-3656e9ffdca4 devices: root: path: / pool: local type: disk ephemeral: false profiles: - default stateful: false description: '' created_at: '2026-01-18T10:14:25.387442471Z' name: wolf status: Running status_code: 103 last_used_at: '2026-01-23T18:42:58.822982934Z' location: none type: container project: default ``` Podman: ``` [Unit] Description=Wolf / Games On Whales Requires=network-online.target podman.socket After=network-online.target podman.socket [Service] TimeoutStartSec=900 ExecStartPre=-/usr/bin/podman rm --force WolfPulseAudio Restart=on-failure RestartSec=5 StartLimitBurst=5 [Container] AutoUpdate=registry ContainerName=%p HostName=%p Image=ghcr.io/games-on-whales/wolf:stable Network=host SecurityLabelDisable=true PodmanArgs=--ipc=host --device-cgroup-rule "c 13:* rmw" AddDevice=/dev/dri Volume=/mnt/dev:/dev:rw Volume=/mnt/udev:/run/udev:rw Volume=/etc/wolf/:/etc/wolf:z Volume=/run/podman/podman.sock:/var/run/docker.sock:ro #Environment=WOLF_STOP_CONTAINER_ON_EXIT=TRUE Environment=WOLF_LOG_LEVEL=DEBUG [Install] WantedBy=multi-user.target ``` Output logs are attached, any help would be greatly appreciated! [log0.txt](https://github.com/user-attachments/files/24828219/log0.txt) [log1.txt](https://github.com/user-attachments/files/24828220/log1.txt)

bsakaguchi commented

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

Author

Owner

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

Unfortunately, your logs show that annoying [31B blob data] which doesn't mean anything. Are you getting those logs from a UI by any chance? If you get them via CLI you should be able to see the actual messages from the dying Steam container.

As for what the actual issue is, I feel this might be tied to https://github.com/games-on-whales/wolf/issues/330 can you try running the Steam image from this PR https://github.com/games-on-whales/gow/pull/282 ? Does any other image work btw or is this just an issue with Steam?

@ABeltramo commented on GitHub (Jan 26, 2026): Unfortunately, your logs show that annoying `[31B blob data]` which doesn't mean anything. Are you getting those logs from a UI by any chance? If you get them via CLI you should be able to see the actual messages from the dying Steam container. As for what the actual issue is, I feel this might be tied to https://github.com/games-on-whales/wolf/issues/330 can you try running the Steam image from this PR https://github.com/games-on-whales/gow/pull/282 ? Does any other image work btw or is this just an issue with Steam?

bsakaguchi commented

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

Author

Owner

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

Thank you for your reply 🙏

I was using journalctl. Maybe this is more helpful?

log2.txt

At the weekend I will give the suggested steam image a try!

@amaccuish commented on GitHub (Jan 29, 2026): Thank you for your reply 🙏 I was using journalctl. Maybe this is more helpful? [log2.txt](https://github.com/user-attachments/files/24947065/log2.txt) At the weekend I will give the suggested steam image a try!

bsakaguchi commented

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

Author

Owner

@amaccuish commented on GitHub (Feb 1, 2026):

At least I see an error now, it's complaining about the lack of libc.so.6.

Would any of the backtraces I came across in /etc/wolf/cfg be of use?

@amaccuish commented on GitHub (Feb 1, 2026): At least I see an error now, it's complaining about the lack of libc.so.6. Would any of the backtraces I came across in /etc/wolf/cfg be of use? <img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/493c361a-2991-4101-96b6-84ec36ae40a0" />