Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

localstack fails to properly log under podman.

Starting logstack when using podman will generate the following error in the console:

⠼ Starting LocalStack container2025-01-28T19:11:00.121 DEBUG --- [-log-printer] localstack.utils.run       : Executing command: ['docker', 'logs', '261b4f90dcc37e74bce5b97cf390a7b935fc2d1e0d12ecd41c8df632b7587e76', '--follow']
────────────────────────────────────────────────────────────────────────────────── LocalStack Runtime Log (press CTRL-C to quit) ─────────────────────────────────────────────────────────────────────────────────── 
Error: no container with name or ID "--follow" found: no such container 

After this error, no further logs are printed to the console

podman is sensitive to the position of the -f or --follow argument.

Expected Behavior

It is expected localstack will print logging normally to the console when using podman, just as it does under docker

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)

localstack start

Environment

- OS: Fedora 40 (x86_64)
- LocalStack:
  LocalStack version: 4.0.4.dev144
  LocalStack Docker image sha: 31a99acf3a5f
  LocalStack build date: 2025-01-28T15:10:15
  LocalStack build git hash: 25b920c14

Anything else?

I have created a PR to fix this issue here:
#12200