You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note the first thing that I did was install Rosetta2, homebrew, and get my terminal up and running w/ x86. I tried with arch --arm64 ./run_mtgo and unfortunately that yielded the same results.
I can't get the environment to start at all. Before using --winecfg option, I wasn't able to get a window up at all. Only after enabling the desktop was I able to see the desktop. After that, it seems to get into a "bootloop" (self-contained to the container) of seg faults.
OS: MacOS; Sonoma 14.5
Chip: Apple M3
Graphics card: Apple M3-Built-In
Output of docker info:
Client:
Version: 26.1.4
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.14.1-desktop.1
Path: /Users/charliestein/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.27.1-desktop.1
Path: /Users/charliestein/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.32
Path: /Users/charliestein/.docker/cli-plugins/docker-debug
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/charliestein/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.24
Path: /Users/charliestein/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /Users/charliestein/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.2.0
Path: /Users/charliestein/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/charliestein/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.9.3
Path: /Users/charliestein/.docker/cli-plugins/docker-scout
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 26.1.4
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: d2d58213f83a351ca8f528a95fbd145f5654e957
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.6.31-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 8
Total Memory: 7.657GiB
Name: docker-desktop
ID: e4609f03-11b8-4e2e-901c-82fa858a2dd3
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///Users/charliestein/Library/Containers/com.docker.docker/Data/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
Update, using shell, I'm seeing the following error. Maybe some improper staging, but not sure. Investigating further.
`wine@docker-desktop:~$ wine --debug /opt/mtgo/mtgo.exe
2024/07/07 00:06:14 socat[15204] W waitpid(-1, {}, WNOHANG): no child has exited
wine: could not open working directory L"unix\home\wine\", starting in the Windows directory.
Application could not be started, or no application associated with the spe
cified file.
ShellExecuteEx failed: File not found.
Hello!
Note the first thing that I did was install Rosetta2, homebrew, and get my terminal up and running w/ x86. I tried with
arch --arm64 ./run_mtgo
and unfortunately that yielded the same results.I can't get the environment to start at all. Before using
--winecfg
option, I wasn't able to get a window up at all. Only after enabling the desktop was I able to see the desktop. After that, it seems to get into a "bootloop" (self-contained to the container) of seg faults.OS: MacOS; Sonoma 14.5
Chip: Apple M3
Graphics card: Apple M3-Built-In
Output of
docker info
:output.log
The text was updated successfully, but these errors were encountered: