Fix docker build slowness and disk bloat #35
No reviewers
telackey
Labels
No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/hosting#35
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "dboreham/use-overlay2-docker-driver"
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?
Mount an anonymous volume at /var/lib/docker. This has the side effect of causing the docker daemon inside the executor container to use overlay2 for its storage driver. Without this docker uses vfs for its storage driver. The impact of this is significant on the container build process because docker relies on the storage driver to implement a layer delta storage scheme. Without that feature in the storage driver, a fall back implementation where each layer is a complete snapshot of the entire image contents is used. This means for example that when building a 1G image with 10 layers, you end up with 10G of data, copied 10 times. But if overlay2 is used, with its capability to store only image differences, the same workload results in approximately 1G of storage and almost no copying.