fix(deploy): purge le cache de build Docker après chaque déploiement - #31
Merged
Merged
Conversation
docker image prune -f ne touche pas le cache de build (couches intermédiaires), qui grossissait sans limite à chaque build sur ce serveur à faible disque - 13,5 Go accumulés en ~2 jours, faisant passer l'usage disque de 18% à 73%. Ajoute un docker builder prune avec fenêtre de 24h (garde le cache utile aux rebuilds du jour, purge le reste).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Résumé
deploy.sh --run) faisait déjà undocker image prune -faprès chaque build réussi, mais ça ne touche pas le cache de build Docker (couches intermédiaires du multi-stage build).docker builder prune -f --filter "until=24h"après le déploiement : garde le cache récent (utile si on redéploie plusieurs fois la même journée) et purge le reste automatiquement à chaque tick.Test plan
docker builder prune -f+docker image prune -a -f), disque repassé de 73% à 18%, conteneurs vérifiés toujours up sans interruption.docker builder pruneapparaît bien dansdeploy.loget que le disque reste stable dans le temps.🤖 Generated with Claude Code
https://claude.ai/code/session_01BFeFP2FpeQbaHC7qA6Y59r