Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Volume path overlap with existing paths inside image

Abierto
  • ¿Algo no está bien?
#162 2 comentarios 0 reacciones 0 asignados Ver en GitHub

@pe1uca ya está trabajando en esto.

Desde el 30/6/2026.

  • #164 de @pe1uca — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
docker, php, sqlite
Área
database, infrastructure

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Shell
Estrellas
527
Forks
72
Sin PR fusionados en 30 d

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de LinkStackOrg/linkstack-docker

Todos los issues de LinkStackOrg/linkstack-docker

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.