affinity mask must specify at least one bit crash preventing Zilla from starting on Windows 11 + Docker Compose

[clonardo]

Describe the problem
I have been trying to set Zilla up on my Windows 11 workstation with Docker Compose, and have not been able to make any of the examples run.

The common thread has been an error related to affinity (affinity mask must specify at least one bit: REST-example.south_kafka_cache_server 0) when I view the Zilla logs in Docker:

When this happens, the container dies, and will keep dying if restarted. This exception appears to be defined in the EngineWorker's resolveAffinity method.

For the sake of simplicity, I am now focused on the simple 2-file setup for a CRUD API on top of Kafka here. The docker-compose.yaml + zilla.yaml in this repo are identical to what was posted on the Aklivity site as of November 26, 2024.

My docker-compose is working fine for everything else on my machine. Thanks in advance for taking a look!

To Reproduce
Steps to reproduce the behavior:

• Clone this repo I created showing the issue: https://github.com/clonardo/zilla-test
• From the repo root, run docker-compose up -d
• View the logs of the zilla container in Docker

Of note:

• While this zilla.yaml file is exactly as it was shown on the Aklivity site, as I was fiddling with versions of the config, I saw the same affinity failure across the http server as well as the Kafka cache server
• Depending on what the state of your config is in, sometimes it won't fail until an http request comes into the Zilla gateway (e.g., GET on localhost:7114/api/items)- otherwise it will log the config and then fall over

Expected behavior
The example should build and run without crashing or throwing a cryptic error

Zilla Environment:
Environment Details

• Host OS: Windows 11 (fully up to date)
• Docker version 27.3.1 with wsl 2.3.26.0 (latest) backend
• JDK: openjdk 21.0.5 2024-10-15 LTS
• Launched with docker-compose up -d , and the docker-compose file runs start -ve for the Zilla container

Describe a docker container:

docker inspect <zilla container name> | jq -r '.[].Config' 

	"Config": {
		"Hostname": "2f8f831925f5",
		"Domainname": "",
		"User": "",
		"AttachStdin": false,
		"AttachStdout": true,
		"AttachStderr": true,
		"ExposedPorts": {
			"7114/tcp": {}
		},
		"Tty": false,
		"OpenStdin": false,
		"StdinOnce": false,
		"Env": [
			"KAFKA_BOOTSTRAP_SERVER=kafka:29092",
			"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
			"ZILLA_VERSION=0.9.102"
		],
		"Cmd": [
			"start",
			"-v",
			"-e"
		],
		"Image": "ghcr.io/aklivity/zilla:latest",
		"Volumes": null,
		"WorkingDir": "",
		"Entrypoint": [
			"/opt/zilla/zilla"
		],
		"OnBuild": null,
		"Labels": {
			"com.docker.compose.config-hash": "692478139f8e6e9c63d7fd1c7ba2b60b3bc149152dd8110830044c2d6071a0c7",
			"com.docker.compose.container-number": "1",
			"com.docker.compose.depends_on": "kafka:service_started:false",
			"com.docker.compose.image": "sha256:a424304281f786c30c0651486e29622fd8b998ce5666140d567a981285fe1dc9",
			"com.docker.compose.oneoff": "False",
			"com.docker.compose.project": "zilla-test",
			"com.docker.compose.project.config_files": "C:\\lancaster\\zilla-test\\docker-compose.yaml",
			"com.docker.compose.project.working_dir": "C:\\lancaster\\zilla-test",
			"com.docker.compose.service": "zilla",
			"com.docker.compose.version": "2.29.2",
			"org.opencontainers.image.ref.name": "ubuntu",
			"org.opencontainers.image.version": "22.04"
		}
	}

[clonardo]

Tried this on another Windows 11 machine and it works- looks like a Docker/Windows issue on my side. Closing.