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

Volume path overlap with existing paths inside image

Open
  • Is something wrong?
#162 2 comments 0 reactions 0 assignees View on GitHub

@pe1uca is already working on this.

Since Jun 30, 2026.

  • #164 by @pe1uca — open

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, php, sqlite
Domain
database, infrastructure

Research direction

Read the container configuration and the LinkStack application setup to find how /htdocs is mounted and where the SQLite database is configured or seeded. Check the existing volume definitions and startup process first. Done means the database can use its own configurable location, is created at container start, and only /htdocs/storage/app/public needs to persist uploaded files.

Written by the indexing model from the issue text.

Description

The /htdocs webroot inside the container is currently recommended to be configured as volume. However since it contains files required for the application to function, it causes issues with very common use-cases which override the volume content at mount, leaving an empty directory.

The following use-cases are currently impossible without workarounds (see below):

  • Bind volumes with Docker/Podman/Compose
  • Kubernetes volumes

A workaround is to copy the original content of the image in the volume with an init container, prior to the main container starting. But this rather hacky and not ideal.

The following changes would be required at minimum:

  • Allow defining the location of the SQLite database file: that way it can be configured to be read from its own dedicated (sub-)directory and configured as volume
    • I see a non-empty database is already present on the image's FS. If it is somehow seeded and built into the app that's also bad practice and instead it should be created from scratch at container start
  • Only mount /htdocs/storage/app/public as a volume to persist file uploads: AFAIK the rest of the webroot doesn't need to be persisted
Dominant language
Shell
Stars
527
Forks
72
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 LinkStackOrg/linkstack-docker

All issues in LinkStackOrg/linkstack-docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.