chore: Docker image prune im Drone-Deploy gegen Disk-Voll-Laufen #354
Labels
No labels
app/archiv
app/einkaufslisten
app/imap-client
app/wissensbasis
arch-answered
arch-question
area/api
area/auth
area/infra
area/mobile
area/shared
area/ui
area/web
portfolio-status
prio/high
prio/low
prio/medium
roadmap/public
size/l
size/m
size/s
size/xl
size/xs
status/blocked
status/needs-info
type/bug
type/chore
type/docs
type/feature
type/idea
type/refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
admin-mrrm/mrrmlabapp#354
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Folgemaßnahme aus dem Cleanup-Lauf nach #352:
prod-altlief bei 97% Disk-Usage;docker image prune -fhat 20 GB freigegeben (362 dangling Images, davon zig 5.67 GB OCR-Snapshots). Pro Deploy entstehen ~6 GB dangling Layer (ocr+api+web).Fix:
docker image prune -fals zusätzlichen Schritt in dendeploy- unddeploy-dev-Pipelines nachdocker compose up -d.