Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@LuigiARC
Copy link
Contributor

Should fix #166. I just applied the fix that @xrexy provided in the issue mentioned.
(first time i'm opening a pr on a public project so let me know if i'm doing it right c:)

@TibixDev
Copy link
Owner

Thank you, merging this! 🙌

@TibixDev TibixDev merged commit 1dc8c00 into TibixDev:main Sep 23, 2025
@realitymolder
Copy link

Thanks, did you manage to create a vm with that installation? I'm getting docker permission issues on installation for some reason.

@LuigiARC
Copy link
Contributor Author

LuigiARC commented Sep 23, 2025

I was able to go through the setup and am actively using the VM as I type this, yes. I'll do some further testing later today or tomorrow.

@LuigiARC
Copy link
Contributor Author

Thanks, did you manage to create a vm with that installation? I'm getting docker permission issues on installation for some reason.

Only thing I can think of the top of my head right now is: if it's permission issues, make sure you can run docker commands without sudo (add your user to the docker group on your configuration.nix if you haven't) @toubul

@realitymolder
Copy link

Thanks, did you manage to create a vm with that installation? I'm getting docker permission issues on installation for some reason.

Only thing I can think of the top of my head right now is: if it's permission issues, make sure you can run docker commands without sudo (add your user to the docker group on your configuration.nix if you haven't) @toubul

umm interesting.
I don't know to be honest. I absolutely did add my user into the docker group. That is why I created the issue where the docker group wont be read well in the appimage / flake.
After the last update I've managed to enter to the VM creation assistant / screen - but then the vm creation crashes, and in the logs im getting some permission error, maybe this is relevant to the USB lib? (because of the path)

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error creating device nodes: open /home/daniel/.local/share/docker/overlay2/04006f233d17d26f740f11e4f18e842d36fe43e61077bb31057363e4d35dba5c/merged/dev/bus/usb/001/001: permission denied: unknown

I would add that it says in the UI that the container was created but WinBoat Guest API - Offline

@LuigiARC
Copy link
Contributor Author

That looks to me like a docker response rather than a winboat thing. I don't really have any idea why this could be happening though. Maybe manually creating a dockur/windows docker vm would show more verbose logging?

@xrexy
Copy link

xrexy commented Sep 23, 2025

Only thing I can thing of is if your user doesn't have the dialout group @toubul. Can you send the output from id -Gn

@realitymolder
Copy link

realitymolder commented Sep 23, 2025

Only thing I can thing of is if your user doesn't have the dialout group @toubul. Can you send the output from id -Gn

Oh, first time I hear about the dialout group.

Response for id -Gn : users wheel audio video networkmanager docker input kvm

Update: working, was an issue due to init with rootless docker.

waffles-dev pushed a commit that referenced this pull request Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] winboat won't read docker group on nixos ?

4 participants