[BUG] Custom deploy script for using certs in other containers
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- docker, nginx, shell
- Área
- devops, infrastructure
Línea de trabajo
The failure is in the deploy hook at /config/etc/letsencrypt/renewal-hooks/deploy/20-reload, which calls docker before the universal-docker mod has installed the binary. The container's init ordering, where mods are applied relative to the certbot renewal step, is the part to investigate. Done means the hook can run docker on the first renewal after container start. Reproducing requires a Docker environment with the mod and a forced renewal.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I have installed swag docker with linuxserver/mods:universal-docker mod
So that I can have docker command inside swag repository, for restarting other docker services, after certificate change.
But I have found out that the mods are installed after the certificate is renewed, and after the deploy hooks have run. Therefore on swag start they would error out.
Hook will work on the next run the next month when the next renewal will start.
Expected Behavior
The mods should be installed before certificate renewal process
Steps To Reproduce
- Create custom deploy hook that is using docker command
- Change for example SUBDOMAINS so that new certificate is needed
- Observe as hook errors out with docker command not found
- Observe installation of docker mod
Environment
- OS: Debian GNU/Linux 12
- How docker service was installed: apt, docker
CPU architecture
arm64
Docker creation
services:
swag:
container_name: swag
image: lscr.io/linuxserver/swag:5.9.0
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- URL=XXX
- VALIDATION=dns
- SUBDOMAINS=X,XX,XXX #optional
# - CERTPROVIDER= #optional
- DNSPLUGIN=cloudflare #optional
# - PROPAGATION=120 #optional
- [email protected] #optional
- ONLY_SUBDOMAINS=true #optional
# - EXTRA_DOMAINS= #optional
- STAGING=false #optional
- DISABLE_F2B=true #optional
- SWAG_AUTORELOAD=true #optional
# - SWAG_AUTORELOAD_WATCHLIST= #optional
- DOCKER_MODS=linuxserver/mods:universal-docker|linuxserver/mods:swag-dashboard
volumes:
- ./config:/config
- '/var/run/docker.sock:/var/run/docker.sock'
- ./modcache:/modcache
dns:
- 1.1.1.1
networks:
vlan:
ipv4_address: X.X.X.X
restart: unless-stopped
networks:
vlan:
external: true
Container logs
These files will be updated when the certificate renews.
NEXT STEPS:
- The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
* Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
* Donating to EFF: https://eff.org/donate-le
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Reloading certificates
/config/etc/letsencrypt/renewal-hooks/deploy/20-reload: line 7: docker: command not found
/config/etc/letsencrypt/renewal-hooks/deploy/20-reload: line 12: docker: command not found
New certificate generated; starting nginx
The cert does not expire within the next day. Letting the cron script handle the renewal attempts.
**** Applying the SWAG dashboard mod... ****
**** installing docker and docker compose ****
Copying over docker and docker-compose binaries
**** Adding goaccess to package install list ****
**** libmaxminddb already installed, skipping ****
**** Applied the SWAG dashboard mod ****
[pkg-install-init] **** Installing all mod packages ****
(1/1) Installing goaccess (1.10.2-r0)
Executing busybox-1.37.0-r31.trigger
OK: 219.2 MiB in 219 packages
[custom-init] No custom files found, skipping...
Auto-reload: Watching the following folders for changes to .conf files:
/config/nginx
- Lenguaje dominante
- Dockerfile
- Estrellas
- 3.8k
- Forks
- 274
- Merge medio
- 25 min
- PR fusionados (30 d)
- 1
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de linuxserver/docker-swag
-
no-issue-activity
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
linuxserver/docker-swag#631 · 2 comentarios ·
-
[BUG] Anonymous Authelia redirects can overwrite a newer login sessionPosiblemente ocupada @MeiXu6693 la tomó hace 20 días. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
linuxserver/docker-swag#634 · 1 comentario ·
-
no-issue-activity
Dificultad 4/5 1-2 días Aptitud para principiantes 25/100
linuxserver/docker-swag#630 · 3 comentarios ·
-
[BUG] "chmod: changing permissions of '/XXX': Bad address" error message (QNAP)Quizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abiertobug upstream issue work-in-progress
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
linuxserver/docker-swag#514 · 75 comentarios ·
-
awaiting-approval
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
linuxserver/docker-swag#276 · 7 comentarios · 6 reacciones ·
Todos los issues de linuxserver/docker-swag
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
soroswap/token-list#125 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
nekko-labs/nekko-agent#2998 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
francescopace/espectre#222 ·
Los mantenedores suelen responder en 3 días
-
good first issue ops security
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Kyvera-Labs/verixa#565 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día