Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't work on Apple M1 chip #63

Closed
kus opened this issue Nov 16, 2023 · 2 comments
Closed

Doesn't work on Apple M1 chip #63

kus opened this issue Nov 16, 2023 · 2 comments

Comments

@kus
Copy link

kus commented Nov 16, 2023

I know it's not your repo, but just curious if you know anyone who has successfully gotten this to run on an Apple M1 chip?

Steamcmd behaves very weirdly. You first get this error Unable to determine CPU Frequency. Try defining CPU_MHZ. so I define the environment variable with --env CPU_MHZ=2500 then that error goes away, but it won't actually download a game.

You get lots of errors like this src/common/processpipe_posix.cpp (279) : invalid name/address:port string provided to BSetIpPortFromName SteamClientService_25

I launch docker with this command:

docker run --env CPU_MHZ=2500 -p 27015:27015 --platform linux/amd64 joedwards32/cs2

I've tried setting up a bare bones docker image running Ubuntu and Steamcmd and can't get it to work either, but the same bash script works on Google Cloud on a Ubuntu VM.

Any ideas of anything I should try?

@yannickvr
Copy link

AFAIK M1 chips are ARM architecture and CS requires X86 architecture. I think there are ways for running things in x86 mode on M1, slow as hell, but it might fix it for you.

@joedwards32
Copy link
Owner

--platform linux/amd64 tells Docker to use macOS' Rosetta x86_64 emulation when running the container. This isn't perfect and there will be bugs with some applications.

If you are set on running the container on your M1 device, you could try running a QEMU VM and hope that the QEMU x64_64 emulation is OK.

If you are prepared to use Google Cloud or AWS then I recommend running the container under one of their serverless containerisation services. E.g. AWS Fargate.

Marking this issue as closed as CS2 M1 support isn't within the scope of this project.

Gd luck :)

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

No branches or pull requests

3 participants