astro dev start - failing in podman on fedora 43

[NewtonChutney]

Describe the bug

I tried setting up airflow on fedora 43, but i get this error:

[+] Running 6/6
 ✘ scheduler Error     denied: requested access to the resource is denied                                                                                     3.6s 
 ✘ dag-processor Error denied: requested access to the resource is denied                                                                                     3.6s 
 ✘ triggerer Error     denied: requested access to the resource is denied                                                                                     3.6s 
 ✘ postgres Error      denied: requested access to the resource is denied                                                                                     3.6s 
 ✘ api-server Error    denied: requested access to the resource is denied                                                                                     3.6s 
 ✘ db-migration Error  denied: requested access to the resource is denied                                                                                     3.6s 
Error: error building, (re)creating or starting project containers: Error response from daemon: denied: requested access to the resource is denied

Full log

fsh ❯ astro dev start --verbosity debug
STEP 1/1: FROM astrocrpublic.azurecr.io/runtime:3.1-9
Trying to pull astrocrpublic.azurecr.io/runtime:3.1-9...
Getting image source signatures
Copying blob bc0a940f9b2a skipped: already exists  
Copying blob 79411a5fb0b9 skipped: already exists  
Copying blob dfc47e62263b skipped: already exists  
Copying blob b54db5b2ff30 skipped: already exists  
Copying blob 31018fa55ed0 skipped: already exists  
Copying blob eb4af807f98b skipped: already exists  
Copying blob 59e84d916894 skipped: already exists  
Copying blob bd09064ee8d8 skipped: already exists  
Copying blob 8fd394e4cb24 skipped: already exists  
Copying blob 60cf60556609 skipped: already exists  
Copying blob 6f3e42e2dc7a skipped: already exists  
Copying blob 88694c48cbb0 skipped: already exists  
Copying blob 6f0f4539d50a skipped: already exists  
Copying blob cd196efaa86c skipped: already exists  
Copying blob 4e7e1f39aa33 skipped: already exists  
Copying blob 6cb8dbcb9c99 skipped: already exists  
Copying blob 803df5fbe2e9 skipped: already exists  
Copying blob 818b5a32a599 skipped: already exists  
Copying blob 61bd50cadb3e skipped: already exists  
Copying blob 518328f6d18e skipped: already exists  
Copying blob 01584b743a9b skipped: already exists  
Copying blob 74b88414e0a8 skipped: already exists  
Copying blob 355ae31fe789 skipped: already exists  
Copying blob 25cb2f0a5502 skipped: already exists  
Copying blob bd9ddc54bea9 skipped: already exists  
Copying blob a6c5284d9c8b skipped: already exists  
Copying blob 5d4efcc43e7f skipped: already exists  
Copying blob a4093bc544bb skipped: already exists  
Copying blob 227cb9fda5ea skipped: already exists  
Copying config 409f34f456 done   | 
Writing manifest to image destination
STEP 2/8: COPY packages.txt .
--> Using cache 4c4497a0624bd53eae02c65666087765df9ae4cc318cae56dc0fb86799a6c23c
--> 4c4497a0624b
STEP 3/8: USER root
--> Using cache 11e392da8bcac15bf3d45381c8998d9cca9367bba2b7bac97aa3af289047b4e0
--> 11e392da8bca
STEP 4/8: RUN /usr/local/bin/install-system-packages
--> Using cache 371d341dbeef363139500d6e8f91e1539680f067ec81ba5301b8b270d2b0d3fe
--> 371d341dbeef
STEP 5/8: COPY requirements.txt .
--> Using cache 6f5c739d71e86aa69b7a5319dcdded5142f0a631a6bd3eab90025d80cbeabbbe
--> 6f5c739d71e8
STEP 6/8: RUN /usr/local/bin/install-python-dependencies
--> Using cache 3a853ab00f94aade6d2410a2a6f07afd77b277e64500531e854724f225074aec
--> 3a853ab00f94
STEP 7/8: USER astro
--> Using cache 3f1d68ded28a1ea24c52e532072564b487cf011da990f3e4af4cae275b9592b6
--> 3f1d68ded28a
STEP 8/8: COPY --chown=astro:0 . .
--> Using cache 4ce749944e901a8a5eb7fb34f5e9ec28e46d496b5dc20c288355f7c40d7dc7ba
COMMIT airflow-dev_1ee11f/airflow:latest
--> 4ce749944e90
Successfully tagged localhost/airflow-dev_1ee11f/airflow:latest
4ce749944e901a8a5eb7fb34f5e9ec28e46d496b5dc20c288355f7c40d7dc7ba
✔ Project image has been updated
DEBU[0012] Env file ".env" found. Loading...            
[+] Running 6/6
 ✘ scheduler Error     denied: requested access to the resource is denied                                                                                                                                                  3.6s 
 ✘ dag-processor Error denied: requested access to the resource is denied                                                                                                                                                  3.6s 
 ✘ triggerer Error     denied: requested access to the resource is denied                                                                                                                                                  3.6s 
 ✘ postgres Error      denied: requested access to the resource is denied                                                                                                                                                  3.6s 
 ✘ api-server Error    denied: requested access to the resource is denied                                                                                                                                                  3.6s 
 ✘ db-migration Error  denied: requested access to the resource is denied                                                                                                                                                  3.6s 
Error: error building, (re)creating or starting project containers: Error response from daemon: denied: requested access to the resource is denied

What CLI Version did you experience this bug?
Astro CLI Version: 1.38.1

This CLI bug is related to which Astronomer Platform?

• Astro
• Software
• None/Unknown

What Operating System is the above CLI installed on?

fsh ❯ cat /etc/os-release 
NAME="Fedora Linux"
VERSION="43 (Workstation Edition)"

🪜 Steps To Reproduce

Run astro init and then astro dev start on Fedora 43.
The image was built properly, and running the test postgres image from the docs created volumes successfully (screenshot below), but I'm unable to understand which resource failed to get accessed.

📸 Screenshots