Running on M1 about aerospike-server.docker HOT 9 CLOSED

Was there any permision issue with /sys/devices/system/cpu/cpu0/topology/physical_package_id? (should have read permission for all)
Did the customer try the docker run with 'sudo'?

from aerospike-server.docker.

Could you try again - be sure to re-pull the image.

An earlier release had shipped tini for x86_64 instead of aarch64. I'm unsure how that failure manifested, oddly the image worked fine when emulating aarch64. Just want to be sure this isn't something we've already addressed.

We have tried internally with a Mac with an M1 processor and it worked for us - not sure what is different between your environment and ours. If the issue continues, having more details about your environment could be helpful (such as OSX version and docker-desktop version).

from aerospike-server.docker.

I remove docker image and pull it again. The same problem. Also try to run docker with sudo, not helped =\

About my versions:
macos 13.0.1 (22A400)
docker 4.14.1 (91661)
docker engine 20.10.21
docker compose v2.12.2

from aerospike-server.docker.

The system we tested on differed only by the macos version - 12.5.1. I'll see if anyone has upgraded to Ventura can attempt to repro this issue.

from aerospike-server.docker.

Not finding any M1 Macs running Ventura and hesitant to upgrade to Ventura this early. Have you tried running the container in privileged mode or maybe --security-opt systempaths=unconfined.

from aerospike-server.docker.

Ok, found a M1 Mac running Ventura and tested this image on that machine - ran without issue.

Suggestion is that your docker-desktop is corrupted, which apparently is a common issue. Recommendation is to completely uninstall and reinstall docker-desktop and associated files.

from aerospike-server.docker.

If this issue does continue after resetting docker, running with the hardware logging context in detail could be helpful.

logging {
    console {
        context any info
        context hardware detail
    }
}

Also if you could start a debian:bullseye-slim container and print the share the contents of /sys/devices/system/cpu/cpu0/topology/physical_package_id - that would be interesting. I would expect it to be 0 on your machine. According to the critical, it is outside of the range (0-1023).

from aerospike-server.docker.

I have Apple M1 with Ventura. Aerospike server 6.2.0.1 works fine, at least without any startup errors.
MacOS 13.0.1
docker desktop 4.14.1
docker engine 20.10.21
cat /sys/devices/system/cpu/cpu0/topology/physical_package_id returns 0

from aerospike-server.docker.

I reinstall docker, now everything is ok. Thanks a lot!

from aerospike-server.docker.