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?
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_dirclass 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?