"Bad system call" whatever I try

Questions about Wine on Linux
Locked
goingcrazy
Newbie
Newbie
Posts: 4
Joined: Thu Jan 04, 2024 1:41 am

"Bad system call" whatever I try

Post by goingcrazy »

I'm trying to set up a docker image with wine on Gitpod and I'm failing miserably.
Tried several "recipes" but I always end up with "Bad system call" when I try to run wine.

Ver 1.
Using Gitpod's official gitpod/workspace-full-vnc + installing wine in the workspace by following the instructions from https://wiki.winehq.org/Ubuntu. Had to remove a bunch of included repositories, held up packages and tinker with aptitude (apt refuses to install wine no matter what) but I finally did it. Result - bad system call for wine and winecfg
Ver 2.
Clean Gitpod image from ubuntu/xubuntu and instructions from here https://github.com/hectorm/docker-wine, builds without warnings but, again, bad system call for wine and winecfg
Ver 3.
Using older version as suggested here viewtopic.php?p=142449
Set up to use buster since the original uses jessie which is now archived
Builds but, once again, bad system call for wine and winecfg

I have no idea how to troubleshoot this.
Thinking of just running windows on qemu.
Any help is much appreciated.
goingcrazy
Newbie
Newbie
Posts: 4
Joined: Thu Jan 04, 2024 1:41 am

Re: "Bad system call" whatever I try

Post by goingcrazy »

BTW, tried to do this in GitHub's codespaces and everything works fine.
What could be the difference between GitHub and Gitpod that ends with such results?
goingcrazy
Newbie
Newbie
Posts: 4
Joined: Thu Jan 04, 2024 1:41 am

Re: "Bad system call" whatever I try

Post by goingcrazy »

Forgot to attach a screenshot on the previous post
Attachments
Screenshot_5.png
goingcrazy
Newbie
Newbie
Posts: 4
Joined: Thu Jan 04, 2024 1:41 am

Re: "Bad system call" whatever I try

Post by goingcrazy »

I've managed to get a reply on Gitpod discord and I'm leaving it here for future references:

"There is a difference in the workspace environment. GitHub CodeSpaces uses a VM (probably a microVM) within which they run a privileged docker container.
On the other hand, Gitpod does not use a dedicated VM for each workspace container, so even though the container runs in privileged mode some restrictions apply for security reasons and proper isolation."

The exact reason is this: https://github.com/gitpod-io/gitpod/issues/7358

TL;DR - you can't run 32bit executables directly in a docker image on Gitpod. So running wine is not an option
Locked