puppetlabs / puppetlabs/puppetlabs-docker
Docker v29 & default containerd storage driver
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 94
- Forks
- 337
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 2
Description
Starting with Docker version 29, the default storage driver uses the containerd image storage (instead of the previous default of overlay2).
With overlay2, the location of the data storage could be controlled with the root_dir class parameter. However, with the new default storage driver, data will get stored in /var/lib/containerd instead. To change where containerd writes its data, you have to make an update to /etc/containerd/config.toml.
Does it make sense to expose this option to the docker module? I looked, and there doesn't appear to be any maintained forge modules for containerd.
Has there been any work/discussion on how to better support this change of default within this puppet module?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Docker module's existing root_dir class parameter and the Docker v29 change to containerd image storage. Then examine the referenced /etc/containerd/config.toml configuration and determine what support the module should expose; done requires an agreed design for configuring the containerd data location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100