`unable to open database file` in DynamoDB image

I am getting the following after starting the DynamoDB container.

```
Initializing DynamoDB Local with the following configuration:
Port: 8000
InMemory: false
Version: 2.6.1
DbPath: /db
SharedDb: true
shouldDelayTransientStatuses: false
CorsParams: null

Jul 03, 2025 4:08:42 PM com.almworks.sqlite4java.Internal log
WARNING: [sqlite] cannot open DB[1]: com.almworks.sqlite4java.SQLiteException: [14] unable to open database file
Jul 03, 2025 4:08:42 PM com.almworks.sqlite4java.Internal log
SEVERE: [sqlite] SQLiteQueue[shared-local-instance.db]: error running job queue
com.almworks.sqlite4java.SQLiteException: [14] unable to open database file
at com.almworks.sqlite4java.SQLiteConnection.open0(SQLiteConnection.java:1480)
at com.almworks.sqlite4java.SQLiteConnection.open(SQLiteConnection.java:282)
at com.almworks.sqlite4java.SQLiteConnection.open(SQLiteConnection.java:293)
at com.almworks.sqlite4java.SQLiteQueue.openConnection(SQLiteQueue.java:464)
at com.almworks.sqlite4java.SQLiteQueue.queueFunction(SQLiteQueue.java:641)
at com.almworks.sqlite4java.SQLiteQueue.runQueue(SQLiteQueue.java:623)
at com.almworks.sqlite4java.SQLiteQueue.access$000(SQLiteQueue.java:77)
at com.almworks.sqlite4java.SQLiteQueue$1.run(SQLiteQueue.java:205)
at java.base/java.lang.Thread.run(Thread.java:840)
```

The `/db` folder is empty inside the container. This might be related to the fact I am using podman in place of docker.

Start by reproducing the DynamoDB container startup with the shown configuration: DbPath /db and SharedDb true, using Podman, then inspect the image's volume and permission setup. Done means identifying a reproducible cause and documenting or fixing the container configuration so SQLite can open the database and /db is usable.

Written by the indexing model from the issue text.