dustymabe added a new comment to an issue you are following:
``
It *could* be an incremental step for #360 if we decided to remove docker from the baked
image eventually. I think this has merits on it's own without considering #360,
though.
The biggest reason I see to do this is for cloud images and having container storage setup
run when people actually wanted to change the defaults. You either have to run some
cloud-init `bootcmd:` to change the container-storage-setup.conf file or you have to tear
down the storage after the fact and then re-run container-storage-setup. Since our setup
now defaults to overlay2 I don't see it as that big of a deal to just have docker
socket activated and then the user doesn't even have to systemctl start docker. Only
downside I see is that the root partition won't get `growpart` on boot. So if you
don't use docker then you would have to manually do that yourself.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/384