bottlerocket-os/bottlerocket

Should the bottlerocket containerd-config.toml file have discard_unpacked_layers set to true by default

Open

#3,314 opened on Aug 3, 2023

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Rust (6,938 stars) (386 forks)batch import
area/corehelp wantedstatus/iceboxtype/enhancement

Description

What I'd like: discard_unpacked_layers to be enabled for containerd by default.

Please see this issue in the default EKS AMI for full details and testing done in that AMI that should apply to Bottlerocket too.

I believe the containerd settings are here for the default version and here for nvidia version.

Any alternatives you've considered: This would require making a custom AMI as described in this issue.

Contributor guide

Tech stack
rust
Domain
infrastructuredevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of containerdFamiliarity with BottlerocketRust (for building)Linux container runtime concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
The issue requests enabling `discard unpacked layers` in containerd config for Bottlerocket. The relevant config files are at packages/containerd/containerd config toml k8s containerd sock and packages/containerd/containerd config toml k8s nvidia containerd sock. The contributor should study the containerd documentation for the discard unpacked layers option, add it with value true in both files, and ensure it does not break existing functionality. The existing GitHub issue #2408 and the linked EKS AMI issue provide context and testing results. No open PRs exist, so the work is unclaimed.