[Bug] Winboat resets itself

[nivaca]

What version of WinBoat are you running?

0.9.0

Your Environment

Operating System: Fedora Linux 43 KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 Kernel Version: 6.17.8-300.fc43.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen AI 7 PRO 350 w/ Radeon 860M Memory: 32 GiB of RAM (23.1 GiB usable) Graphics Processor: AMD Radeon 860M Graphics FreeRDP version 3.17.2 (Flatpak)

Steps to Reproduce / Context

After successfully installing Windows 11 on Winboat, and configuring it, I shut it down. I then reopen it and I get the initial setup wizard. This has been happening lately.

Logs

appUsage.json container.log install.log migrations.log winboat.log

winboat.config.json

Expected Behavior

I would rather have the system starting as I left it.

Current Behavior

Winboat resets itself to zero.

Possible Solution

No response

Quality Notice

• [x] I have checked the issue tracker and verified that this bug is a unique case.

[arfaiz33]

I recently facing the same situation Workaround: Re-create the docker image with docker compose

1. Open terminal
2. navigate to winboat config folder cd ~/.winboat
3. run docker compose up
4. exit the docker compose by pressing Ctrl+C
5. Start the winboat app again

Hope this help

[nivaca]

Thanks, I'm using Podman. I'll try next time with podman compose up.

[Lumaeris]

Same behavior with using Podman.

UPD: I've changed restart value to unless-stopped in podman-compose.yml since podman-compose doesn't recognize no. WinBoat managed to find a container but I'm stuck with a different issue right now since I've used custom ISO, container doesn't recognize custom as a valid value for VERSION. ¯\_(ツ)_/¯ (it was manually updated Win 11 IOT LTSC 2024)

[migranram]

Same here.

The work-aroung from @arfaiz33 solves the issue. Thanks.

[CorentinWicht]

I am experiencing a similar issue. Just reinstalled WinBoat to use Podman instead of Docker and could successfully install W11. When I restarted WinBoat this is what I got:

podman ps returns:

ERRO[0000] OCI Runtime runc is in use by a container, but is not available (not in configuration file or not installed) 
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES

the workaround from @arfaiz33 seems not to work for Podman, podman compose up in ~/.winboat returns:

>>>> Executing external compose provider "/usr/bin/podman-compose". Please refer to the documentation for details. <<<<

podman-compose version: 1.0.6
['podman', '--version', '']
using podman version: 4.9.3
** excluding:  set()
['podman', 'ps', '--filter', 'label=io.podman.compose.project=winboat', '-a', '--format', '{{ index .Labels "io.podman.compose.config-hash"}}']
ERRO[0000] OCI Runtime runc is in use by a container, but is not available (not in configuration file or not installed) 
podman create --name=WinBoat --label io.podman.compose.config-hash=693fd9a708f4bcc12efab4d829d2dd2784b78de2c3372cf8149c569f1fb38e59 --label io.podman.compose.project=winboat --label io.podman.compose.version=1.0.6 --label [email protected] --label com.docker.compose.project=winboat --label com.docker.compose.project.working_dir=/home/USER/.winboat --label com.docker.compose.project.config_files=podman-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=windows --cap-add NET_ADMIN --device /dev/kvm --device /dev/net/tun --device /dev/bus/usb -e VERSION=11 -e RAM_SIZE=16G -e CPU_CORES=6 -e DISK_SIZE=160G -e USERNAME=USER -e PASSWORD=PASSWORD -e HOME=/home/USER -e LANGUAGE=English -e USER_PORTS=7148 -e HOST_PORTS=7149 -e ARGUMENTS=-qmp tcp:0.0.0.0:7149,server,wait=off -v /home/USER/winboat:/storage -v /home/USER:/shared -v /dev/bus/usb:/dev/bus/usb:rslave -v /home/USER/.winboat/oem:/oem --network slirp4netns:port_handler=slirp4netns -p 127.0.0.1::8006 -p 127.0.0.1::7148 -p 127.0.0.1::7149 -p 127.0.0.1::3389/tcp -p 127.0.0.1::3389/udp --privileged --restart on-failure ghcr.io/dockur/windows:5.13
ERRO[0000] OCI Runtime runc is in use by a container, but is not available (not in configuration file or not installed) 
Error: creating container storage: the container name "WinBoat" is already in use by f226351401d956e5c7c0b78f125bac84ad8dbe80e79aa20d51577732e5dc26ec. You have to remove that container to be able to reuse that name: that name is already in use, or use --replace to instruct Podman to do so.
exit code: 125
podman start -a WinBoat
ERRO[0000] OCI Runtime runc is in use by a container, but is not available (not in configuration file or not installed) 
Error: unable to start container f226351401d956e5c7c0b78f125bac84ad8dbe80e79aa20d51577732e5dc26ec: container f226351401d956e5c7c0b78f125bac84ad8dbe80e79aa20d51577732e5dc26ec must be in Created or Stopped state to be started: container state improper
exit code: 125

Any suggestion ?

[CorentinWicht]

Problem solved with sudo apt install runc and podman stop -t 0 WinBoat || true (Ubuntu 24.04 LTS).

Then I could simply restart the container from the WinBoat UI: