Closed mathiasHillmann closed 2 months ago
I'm not sure. Compose looks OK.
Can you clear out the docker image you have downloaded? docker images
and docker rmi
commands. Just to make sure you are using the latest image.
I presume if you run without the -d
flag (i.e. attached) you get the same bash error immediately?
I removed the cached image and volume and this is the result while running without -d
:
steam@mixed:/servers/cs2$ docker-compose up
Creating volume "cs2_cs2" with default driver
Pulling cs2-server (joedwards32/cs2:)...
latest: Pulling from joedwards32/cs2
09f376ebb190: Pull complete
d8997d50f84b: Pull complete
4f4fb700ef54: Pull complete
23e4c21e0e4a: Pull complete
5308617ef2e0: Pull complete
b983151c419d: Pull complete
7fe9e314aa0e: Pull complete
70a1675d4c31: Pull complete
444c8d240377: Pull complete
Digest: sha256:4bf91cebfcfd83c172df821443548dd1f12269ac01b33518270d59c6abea7cd5
Status: Downloaded newer image for joedwards32/cs2:latest
Creating cs2-dedicated ... done
Attaching to cs2-dedicated
cs2-dedicated | exec /usr/bin/bash: no such file or directory
cs2-dedicated exited with code 1
Very odd. Can you try without the persistent volume?
Remove the following from your config
volumes:
- cs2:/home/steam/cs2-dedicated/ # Persistent data volume mount point inside container
I forgot to update this.
I have found out the reason for the odd error was that the VM i'm using is on ARM64 and this container was built for AMD64.
I have the following docker-compose:
And while creating the container no errors appear:
But the container instantly exits with the message:
What am I doing wrong?