I am unsure as to how much of the WinBoat installation procedure is configurable. But here it goes anyway:
Bug
If installing WInboat from the CachyOs Help screen on a system with AppArmor enabled, the WinBoat installation fails towards the last stage when trying to start the container.
Cause
~/.winboat/docker-compose.yml has no provision for AppArmor and the container runs on the more restricted settings.
Expected behavior
docker-compose.yml should be generated with less restrictive options, if AppArmor is detected to be enabled.
Workaround
After the installation fail, do not reset as instructed.
Instead, cd into ~/.winboat/
$ docker compose down
Edit docker-compose.yml and add the following somewhere under the windows: service:
security_opt:
- "apparmor=docker-default"
$ docker compose up -d
It should work now and docker ps should show a running WinBoat image. You can close the WinBoat installation window and start it again.
I guess you are referring to CachyOS Hello, which happens to have a button that opens the debatable CachyOS Package Manager, which in itself a GUI-frontend for pacman.
So you tried to install Winboat (probably because some overhyped influencer was so stoked on it), which requires knowledge about containerized systems and whatnot, using Cachy Package Manager and now you want an easier way to do, what exactly? Have it run nicely together with AppArmor which adds another ton of technical dept?
Wow. Erm… good luck with that, I guess.
Look, I don’t want to be rude, but you are jumping in at the very deep end of the pool. Are you sure you’re not in a bit over your head? Out of curiosity: did you talk to ChatGPT before you wrote that post? Because it sure reads as if you are miles down the LLM rabbit hole.
Ugh. It’s impossible to write anything these days without this chatgpt nonsense popping up every turn.
I was only trying to be helpful after battling with Winboat installation for over an hour. I wasn’t aware I would be drawing the rudes out. Go have a nice day, or whatever it is you do when you are not putting people down.
And I’ll know to stay away from here as much as I can.
Sorry, we seem to have had a bad start, let’s try again.
I just really don’t understand what it is that you are trying to ask here. Is this a feature request? Or a tutorial? I really don’t get it at the moment.
Didn’t mean to be rude (and wrote so), the original post is just a little overwhelming and I really believe you are in deep waters with Winboat and AppArmor and all these things you are piling up on top of each other. To me it just looks like you might have been “guided” by ChatGPT and that it lead you on thin ice. But I might also be mistaken here.
You seem to propose a different behavior of the “Cachy Package Manager”, if I understand your post correctly. But as that is just a nice GUI for pacman, you might be aiming at the wrong target, the Cachy Package Manager does not actually do the installation from what I understand so far. pacman does.
But I could also be totally wrong here.
This is a bit of an overreaction, don’t you think?
After WinBoat is installed by pacman, you have to go through a setup process by firing up Winboat itself. The bug is not in pacman, but in this Winboat setup process: it does not detect that AppArmor is enabled and sets up a docker container that cannot possibly start.
Like I said in my initial post, I don’t know how much of Winboat setup process is configurable. So it is not my intent to tell anyone what to do or how anything should work. I simply wanted to report a problem (that could be potentially fixed by the package maintainer) and the way I eventually found to fix it. I didn’t think I could have made my post clearer.
Well, I am not as much as you’d think. I am not an expert, of course. But it would also help if you didn’t approach every post with the idea that the person has no idea what they are talking about. They do.
It has also had a fancy button added to the Cachy Hello/Welcome application for easy installation.
This package does not automatically handle apparmor integration properly and thus would fail to work in that scenario without extra steps.
@Mario_Figueiredo provided an overview of this problem and a workaround.
It seemed like a fine post.
But I also do not presume to know much about winboat.
I will mention there has been recent movement there with some changes including moving to socket activation and adding the user to the docker group. I am unsure if these may be related to the original post here or not.
But it may be worth saying that the devs hang out on the forum somewhat rarely and you would probably get better results from these kinds of reports going to the github.
Oh boy. I didn’t realize that. Great, more support needed with no-one around. Good Lord.
But it may be worth saying that the devs hang out on the forum somewhat rarely and you would probably get better results from these kinds of reports going to the github.
Yo, that describes the current situation pretty well.
After following your solution, I was able to launch WinBoat. I waited for the installation to finish and had to follow these instructions to restart the WinBoat Guest Server:
Now everything is working fine; I can use tiny11 from CachyOS for Adobe software.