abiosoft / abiosoft/caddy-docker
Convert to Named Volumes
- Lenguaje dominante
- Shell
- Estrellas
- 787
- Forks
- 303
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
This runs great, but is it possible to convert these into named volumes?
```
docker run [...] \
-v $(pwd)/Caddyfile:/etc/Caddyfile \
-v $HOME/.caddy:/root/.caddy \
````
Using Portainer as an example:
```
docker volume create portainer_data
docker run [...] \
-v portainer_data:/data
```
This doesn't quite work but for example:
```
docker volume create caddy_data
# Create file first so Docker doesn't try and make it a folder
touch /var/lib/docker/volumes/caddy_data/Caddyfile
docker run -d \
--name caddy \
-v caddy_data:/root/.caddy \
-v /var/lib/docker/volumes/caddy_data/Caddyfile:/etc/Caddyfile \
-p 80:80 -p 443:443 \
abiosoft/caddy
```
Is this limited due to this [missing feature](https://github.com/moby/moby/issues/32582)?
Thanks!
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
The issue asks about converting bind mounts to named volumes in the Caddy Docker image. Start by examining the Dockerfile and any entrypoint scripts in the repository to understand how Caddyfile and .caddy directory are used. Check if the current setup supports named volumes for files (not just directories) and review the linked moby/moby issue about file volumes. Test with a local Docker setup to see if the workaround using touch works, and verify the container starts correctly with named volumes.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- docker
- Área
- devops
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100