Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unable to create podman container: unable to open database file

Open
  • Is something wrong?
#457 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker
Domain
databases, infrastructure

Research direction

Start with the quadlet at ~/.config/containers/systemd/wallabag.service and inspect the generated command using systemctl --user --no-pager cat wallabag. Check how the mounted /srv/www-wallabag/container/data volume is used during startup; done means systemctl start wallabag creates the container without the unable to open database file error.

Written by the indexing model from the issue text.

Description

When I try to create a podman container of wallabag, using quadlets, the creation of the container quickly fails with unable to open database file

I tried setting the database file and it's directory to be owned by nobody, 75533 (the unamed user the file was originally created as?) and the current user invoking the pod, to no avail

The quadlet file:

[Unit]
Description=Wallabag server

# See Quadlet documentation
[Container]
ContainerName=Wallabag
Image=docker.io/wallabag/wallabag
AutoUpdate=registry
NoNewPrivileges=true
# Recommended volume for Wallabag's persistent data such as configuration and SQLite databases
Volume=/srv/www-wallabag/container/data:/var/www/wallabag/data
# Open a port 8081 on the local machine:
PublishPort=127.0.0.1:8081:8000
Environment=TZ=Europe/Rome
Environment=SYMFONY__ENV__SERVER_NAME="localhost:8081"
Environment=SYMFONY__ENV__DOMAIN_NAME="http://localhost:8081/"
Environment=SYMFONY__ENV__LOCALE=it
Environment=PUID=988
Environment=PGID=988

[Install]
# Start by default on boot
WantedBy=multi-user.target default.target

To reproduce, install the quadlet file in ~/.config/containers/systemd/wallabag.service and run systemctl start wallabag
If you want to clearly see the output, use the cmd line generated by systemd with systemctl --user --no-pager cat wallabag

Dominant language
Shell
Stars
771
Forks
168
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wallabag/docker

All issues in wallabag/docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.