Arch Linux User Repository

The most recent update (0.9.2) has a problem. It was crashing immediately whenever I tried to start it. It had incorrect permissions on /opt/winboat/chrome-sandbox. It works properly when the ownership of chrome-sandbox is changed to root:root and the permissions are changed from 0644 to 4755.

2026-08-26 00:22:39 | INFO | Stopping WinBoat container...
2026-08-26 00:22:47 | INFO | Winboat Guest API went online
2026-08-26 00:22:56 | INFO | Winboat Container state changed to Exited
2026-08-26 00:22:56 | INFO | Destroying Winboat API intervals...
2026-08-26 00:22:56 | INFO | Successfully stopped WinBoat container

Electron startup log:
[96858:0907/143023.427551:WARNING:ui/ozone/platform/wayland/common/drm_render_node_path_finder.cc:111] Preferred drm_render_node not found, picking nvidia-drm
[96858:0907/143023.428956:FATAL:sandbox/linux/suid/client/setuid_sandbox_host.cc:166] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/winboat/chrome-sandbox is owned by root and has mode 4755.
[96861:0907/143023.467342:INFO:third_party/webrtc/rtc_base/cpu_info.cc:77] Available number of cores: 28
[96861:0100/000000.470424:VERBOSE1:content/zygote/zygote_main_linux.cc:202] ZygoteMain: initializing 0 fork delegates
[96861:0100/000000.594666:ERROR:content/zygote/zygote_linux.cc:662] write: Broken pipe (32)

[user@host ~]$ stat -Lc \
    'owner=%U group=%G mode=%a permissions=%A file=%n' \
    /opt/winboat/chrome-sandbox

pacman -Qkk winboat-bin |
    rg 'chrome-sandbox|altered|warning'
owner=root group=root mode=644 permissions=-rw-r--r-- file=/opt/winboat/chrome-sandbox
winboat-bin: 367 total files, 0 altered files
[user@host ~]$ sudo chown root:root /opt/winboat/chrome-sandbox
sudo chmod 4755 /opt/winboat/chrome-sandbox
[sudo: authenticate] Password: 
[user@host ~]$ stat -Lc \    
    'owner=%U group=%G mode=%a permissions=%A file=%n' \
    /opt/winboat/chrome-sandbox
owner=root group=root mode=4755 permissions=-rwsr-xr-x file=/opt/winboat/chrome-sandbox

@w568w fixed, thanks

@ArjixWasTaken

have not added a common provides, e.g. container-compose ?

My purely speculative take is that:

1. podman-compose essentially only parses a subset of the Docker Compose spec and translates it into serial execution of podman subcommands. This leads to inconsistent behavior or feature support (e.g., Podman supports running pods, while Docker does not).
2. Compose is usually an end-user tool, not something typically designed to be invoked or depended by other utilities.
3. For complex scenarios (like winboat), developers effectively need to implement specific compatibility layers to support Podman.

So, rather than calling them drop-in replacements, they are more like two completely independent runtimes. What we're looking for here is essentially a way to declare a dependency on "either one of the two," which likely violates the KISS principle so it’s never been implemented :(

Therefore, the best solution might be to simply ask Podman users to manually edit the PKGBUILD, or just list both docker- and podman-compose as optdepends and use the .install script to prompt the user to install one of them afterwards.

@w568w:

Because docker-compose and its podman counterpart do NOT provide a common metapacakge, maybe you'd like to add a setting item to the PKGBUILD, like this one?

Hmm, such a manual thing is not smth that will get picked up by AUR helpers since it's not part of the SRCINFO, meaning, you could get the same level of customization by using customizepkg, if you still want it to be part of the PKGBUILD then sure, I'll add it

but, I'm curious as to why the Arch maintainers

docker-compose:
- Morten Linderud
- Andrew Crerar
- Lukas Fleischer

podman-compose:
- Filipe Laíns
- David Runge

have not added a common provides, e.g. container-compose ?

(I hate the limited markdown we have here)

(I'm going to repost the comment here since it didn't get any response from the maintainer @matthewq337.)

Since v0.9.0, WinBoat has supported Podman (and podman-compose) as an alternative to Docker (and docker-compose).

So docker-compose is NOT longer a requirement if podman-compose has been installed.

Because docker-compose and its podman counterpart do NOT provide a common metapacakge, maybe you'd like to add a setting item to the PKGBUILD, like this one?

@gitclone navigate to /opt/winboat and execute the winboat binary with ./winboat

how do you use it? after makepkg there is no command to open it?

@ArjixWasTaken you have to update the sha256 to the new version

I am getting the same error as well:

==> Making package: winboat-bin 0.8.3-1 (Tue 23 Sep 2025 23:03:45) ==> Retrieving sources... -> Downloading winboat-0.8.3-amd64.deb... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 95.3M 100 95.3M 0 0 17.0M 0 0:00:05 0:00:05 --:--:-- 20.9M ==> Validating source files with sha256sums... winboat-0.8.3-amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! error: failed to download sources for 'winboat-bin-0.8.3-1': error: packages failed to build: winboat-bin-0.8.3-1

winboat archinux hyperland dont start but AppImage can open [19:24] and update fail too T_T [19:24] ==> Making package: winboat-bin 0.8.3-1 (Mon 22 Sep 2025 07:23:30 PM +07) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found winboat-0.8.3-amd64.deb ==> Validating source files with sha256sums... winboat-0.8.3-amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! -> error making: winboat-bin-exit status 1 -> Failed to install the following packages. Manual intervention is required: winboat-bin - exit status 1