"Command Wine Returned Status 183"

[jmdelahanty]

Hello Winetricks developers! I've been using Winetricks within a Docker image built by @scottyhardy for some processing in a lab I work in with great success on one machine. Unfortunately, while trying to reproduce the image onto another Docker enabled machine I'm running into something that I've been really stuck on.

I've googled for several hours over the past couple days and just can't seem to get this right. I'm still pretty new to this stuff and think it must be something easy, but figured I'd reach out to an expert for some help. I doubt it's something wrong with the repo, but because I can't seem to find an answer to this I thought I would post here in case others run into this problem one day. I would try running winetricks/installing it directly to my computer, but this is on a cluster machine and I don't have permissions to install things like this directly (hence the docker deployment).

For some reason, the moment I execute the build for my Dockerfile, I'm greeted with the following message:

X11 connection rejected because of wrong authentication.

Things then seem to run normally for a couple minutes. Later on in the building process, I'm greeted with these messages:

Executing wine vc_redist.x86.exe /q
0024:err:environ:run_wineboot boot event wait timed out
0024:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
0024:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
006c:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
006c:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
006c:fixme:advapi:DecryptFileW (L"C:\\users\\wineuser\\Temp\\{74d0e5db-b326-4dae-a6b2-445b9de1836e}\\", 00000000): stub
00bc:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
00bc:err:winediag:nodrv_CreateWindow The explorer process failed to start.
00c0:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
00c0:err:winediag:nodrv_CreateWindow The explorer process failed to start.
0024:fixme:ole:CoInitializeSecurity 0032F5F4, -1, 00000000, 00000000, 6, 2, 00000000, 12288, 00000000 stub
00d4:fixme:ver:GetCurrentPackageId (03E0FEF0 00000000): stub
------------------------------------------------------
warning: Note: command wine vc_redist.x86.exe /q returned status 183. Aborting.

This makes me think that there's something going wrong with how this machine has it's X11 settings put together since it's failing to create a window, but after googling for a bit about this error/others I've come up short on how to stop it.

I'd like to see if I can edit the sshd configuration like this post suggests, but I don't have write permissions to that file unfortunately. This stack overflow post seems to suggest the same thing maybe. One link there pointed me to this tutorial but I don't know enough about this to tell if this is the problem.

I came across this issue, but I'm not receiving the specific suggested error message about the Display being set correctly that the Issue submitter sees...

I've also tried what's been suggested here, having the ARG USE_XFB=yes parameter in the Dockerfile, but run into the same error messages. I've also searched high and low for this status 183 message and can't seem to find anyone else in the world who has encountered it let alone fixed it!

Any advice for someone wanting to learn how to troubleshoot this kind of thing?

To Reproduce
Steps to reproduce the behavior:
I have a test Dockerfile that just has this inside it:

# docker-wine is a compatability layer between Windows and Linux.  Allows you to run Windows programs on Linux machines.
FROM scottyhardy/docker-wine:latest

# All credit for this Dockerfile and associated ripping tools goes to Chris Roat, a former software engineer at Stanford in the Deisseroth Lab
# https://github.com/chrisroat
# His work has been adapted for use in the Tye Lab at the Salk Institute by Jeremy Delahanty.
#
# If someone is using the Tye Lab's version, they can contact Jeremy at the email below.
LABEL maintainer="Jeremy Delahanty <[email protected]>"

# This adds about 1.6 GB to the image size.
# The entrypoint wrapper runs the wine setup as wineuser. This is required as it otherwise installs Wine as root causing permission problems later
# The xvfb-run wrapper redirects all displays to a virtual (unseen) display. Wine expects a display to be available.
# Winetricks
# Install visual studio C++ 2015
# This all needs to be run on the same line for some reason, otherwise it crashes
RUN /usr/bin/entrypoint xvfb-run winetricks -q vcrun2015

When I call a Makefile with this inside it:

IMAGE_TAG=20220205
IMAGE_NAME=snlkt-bruker-ripper

build: build_docker

build_docker:
  sudo docker build -t $(IMAGE_NAME):$(IMAGE_TAG) -f Dockerfile .
  sudo docker tag $(IMAGE_NAME):$(IMAGE_TAG) $(IMAGE_NAME):latest

I end up meeting this error message described above.

Expected behavior
On a different machine the build makes it all the way through to where the docker tag command executed!

Desktop (please complete the following information):

Linux tesla 4.19.0-21-amd64 #1 SMP Debian 4.19.249-2 (2022-06-30) x86_64

tesla is managed by SNL Support and runs Debian Buster v10.X.
CPU Count: 40 : "GenuineIntel Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz (2 chips x 10 cores : 20 hyperthread cores)"

[jmdelahanty]

Funny enough I apparently referenced similar things seen in #934 but can't for the life of me see where I actually referenced it in a related issue...

[austin987]

This isn't a winetricks issue. As you pointed out, it's a configuration issue. If anything, the bug is likely in docker-wine/your script, as the problem is that a display isn't set.

[jmdelahanty]

Hello! Thanks for your reply! I'm glad to know it's a config problem. I'll be sure to share with our IT team since they were wondering if it could be something else related to the package and not something with the server's configuration. And also thanks for all your work on this stuff! It's really come in handy for getting some of our workflows in our lab move a lot faster on a cluster!

[jmdelahanty]

See above issue for confirmation of @austin987 's diagnosis and how our IT team solved it!