Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I'm trying to use localstack in Fedora Silverblue 41 using the recommended command from the docs:

DEBUG=1 DOCKER_CMD="podman" DOCKER_SOCK=$XDG_RUNTIME_DIR/podman/podman.sock DOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock localstack start --network podman

but it halts when trying to attach to the container because the container does not exist.

For context, the localstack cli can't download the docker image so I donwloaded it manually with podman pull localstack/localstack so I'm using the image tagged as latest.

Expected Behavior

localstack should start normally.

How are you starting LocalStack?

With the localstack script

Steps To Reproduce

How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)

`DEBUG=1 DOCKER_CMD="podman" DOCKER_SOCK=$XDG_RUNTIME_DIR/podman/podman.sock DOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock localstack start --network podman`

Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

Does not apply

Environment

- OS: Fedora Silverblue 41
- LocalStack:
  LocalStack version: 4.1.1
  LocalStack Docker image sha: fa4257f2b479
  LocalStack build date:
  LocalStack build git hash:

Anything else?

While trying to debug this, I managed to make podman log what happens when the container starts and noticed an error that a directory could not be created due to a permission error. That's how I noticed that this was related to SELINUX. I'm creating this issue just to comply with the guidelines to create a PR.