https://bugzilla.redhat.com/show_bug.cgi?id=1166082
Dusty Mabe <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Dusty Mabe <[email protected]> --- I know it seems odd but I think the reasoning is so that you can configure the storage how you want it before the docker daemon starts (and configures storage automatically in a suboptimal way). The desire is for you to configure storage and then enable docker.service. I think the rationale is that customers will be happier with better performing storage and would prefer that over the one step they have to take to configure and enable the docker service on start. We need to make this easier to understand though (either through documentation, notification, or coming up with a new design). A couple of options: - Document this behavior and promote it. - Create an MOTD that gets displayed on first log in - Actually enable docker.service.. but make docker run after docker-storage-setup.service. This would *require* users to use docker-storage-setup to configure storage (or some script they injected during cloud-init) unless they explicitly disable docker.service during cloud-init. Thoughts? What can we do better? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ golang mailing list [email protected] https://lists.fedoraproject.org/mailman/listinfo/golang
