Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Volume path overlap with existing paths inside image

Aperta
  • Qualcosa non va?
#162 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

@pe1uca ci sta già lavorando.

Dal 30/6/2026.

  • #164 di @pe1uca — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
docker, php, sqlite
Ambito
database, infrastructure

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Shell
Stelle
527
Fork
72
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LinkStackOrg/linkstack-docker

Tutte le issue di LinkStackOrg/linkstack-docker

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.