I cannot reproduce this here, although I do not have access to AWS/EC2; Are you sure whatever is running it has enough disk space? kali-linux-default from the base kali-last-release will take about 7.7GB of space, around 8.8GB total space.

Yep! It's got 100gb disk space available. The amd64 equivalent of this works fine as well.

Can i see your full Dockerfile you're using?

Yep I pasted it in the original description. My dockerfile only consists of this (for testing purposes):

FROM kalilinux/kali-last-release
RUN apt update && apt install kali-linux-default -y

By creating a dockerfile on an ARM64 system and trying to build it, it fails due to the python3.11-minimal error.

Ah, okay, I wasn't sure if there was more; that's a bit odd. You actually would not want to use apt inside it, you'd want to use apt-get. Additionally, you would want to make sure to set the environment variable DEBIAN_FRONTEND=noninteractive so it doesn't ask you any questions.

I still can't reproduce the issue here. An improved dockerfile might be

FROM kalilinux/kali-last-release
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install kali-linux-default -y

Thanks Steev. This is very interesting. That dockerfile sample failed on my arm64 instance in AWS EC2; however, I built that dockerfile with no problems on my M2 Macbook Pro. Guess we can close this one out. Need to do some more investigating on my end to see why it started failing after that recent push to dockerhub from kalilinux.

Noticed my ec2 instance is aarch64 and my M2 MBP is specifically "arm64", so not sure if this has anything to do with it.

aarch64 is the official name of arm64, arm64 is the "common name" and the package architecture for debian systems.

I am curious though, are you really meaning to build against kali-last-snapshot? because those do not get updates once the release is out.

Gotcha - makes sense!

Yup I used to build from kali-last-release on a weekly basis, and one day it failed. I checked dockerhub and noticed that a new image had been pushed to the kalilinux profile about 6 hours prior to that build failing. Haven't been able to get it back up since. Although, I was able to successfully get it to build a few hours ago to my surprise. Only thing I did was update docker, but can't see why that would have fixed it. Same dockerfile.

Could just be some hiccups on my end there, but I'm rebuilding now with the larger dockerfile that I typically use to see if it fails again.

Really appreciate the help on this one!

Glad to hear it's working for you. Feel free to re-open if you can reproduce the issue again, but I've been unable to do so here on multiple machines.