docker-compose
runs old containers and services`docker.errors.DockerException: Error while fetching server API version: {'Connection Aborted.', ConnectionRefusedError(61, 'Connection refused'))`
ERROR: The Compose file './docker-compose.yml' is invalid because: Unsupported config option for services.agent-b: 'extends'
throw new Error("No agents were instantiated probably due to invalid world configuration")
WORLD_SEED
that is invalid (i.e. game is trying to generate a map that breaks some pre-defined rules). Try using another WORLD_SEED
. Examples of broken WORLD_SEED
's include 5555
and 9999
.agent-a
and agent-b
in the docker-compose.yml
file provided in the starter kits.agent-a
is commented out. Un-comment this block to connect a second version of your agent to the game server.base-compose.yml
contains some default services that you can switch out either agent-a
or agent-b
for. If you want to create your own, you will need to create your own Dockerfile (more docs on this here). base-compose.yml
(add the--build
flag to your docker-compose up
command).ValidAgentPacket
described in:TELEMETRY_ENABLED
to 0
(more info on changing environment flags here).fwd
in the docker-compose
files refer to?dev
in the docker-compose
files refer to?dev
mount your host volume to the container. When changes are made to your agent, they will be reflected once you restart the agent container, without needing to rebuild the image. Servers without the dev
label are best for testing your production/submission-ready build.docker-compose
(docs here). Alternatively, you can run the game using docker-compose up --abort-on-container-exit
so that you will not need to exit the containers before restarting them.