Thanks this was helpful, but it did not fully solve it for me. For anyone else that ends up here, the full solution was as follows: Test environment: Ubuntu Server 24.04 ARM64  running in a VM on Macbook M3 Install docker sudo apt install docker.io sudo systemctl enable docker sudo systemctl start docker Pull Splunk Docker Image Have to add --platform option to specify the pull should be done for amd64 architecture.  sudo docker pull --platform=linux/amd64 splunk/splunk:latest Install QEMU  Need to install QEMU so docker can use emulation when running amd64 splunk on arm64 linux host. I took this from docker official documentation here: https://docs.docker.com/build/building/multi-platform/ in section about installing QEMU manually. sudo docker run --privileged --rm tonistiigi/binfmt --install all Run Splunk Docker Image Adding --platform is not necessary here, but it avoids a warning Even though it is not mentioned in the official Splunk documentation (https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/9.3/install-splunk-enterprise-in-virtual-and-containerized-environments/deploy-and-run-splunk-enterprise-inside-a-docker-container) I had to add -e SPLUNK_GENERAL_TERMS=--accept-sgt-current-at-splunk-com because I was getting an error when splunk was starting up. I found the error in the docker logs and it specifically said to add this. Maybe its a new requirement in latest version of splunk. sudo docker run -d --platform=linux/amd64 -p 8000:8000 -e SPLUNK_GENERAL_TERMS=--accept-sgt-current-at-splunk-com -e SPLUNK_START_ARGS='--accept-license' -e SPLUNK_PASSWORD='<insert_password>' --name splunk-enterprise splunk/splunk:latest Note: I initially added --privileged option to above command, but it caused an error in deployment of docker image which was related to app armour and the loaded unix_chkpwd profile which is specific to ubuntu 24.04. The issue was confirmed to be app armor related because running sudo aa-complain unix_chkpwd  command caused the error to just turn into a warning and then the docker container started correctly. For some reason, if you do not add --privileged  option then this issue is non-existent and so far splunk seems to be running fine.   ... View more