Hi,
Just found this:
opened 12:32PM - 08 Nov 18 UTC
<!--
This issue tracker is for *bug reports* and *feature requests*.
For quest… ions, and getting help on using docker:
- Docker documentation - https://docs.docker.com
- Docker Forums - https://forums.docker.com
- Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)
- Post a question on StackOverflow, using the Docker tag
-->
* [x] This is a bug report
* [ ] This is a feature request
* [x] I searched existing issues before opening this one
<!--
DO NOT report security issues publicly! If you suspect you discovered
a security issue, send your report privately to security@docker.com.
-->
### Expected behavior
installing docker using `curl -s https://get.docker.com/ | sh` should work in all common environment.
### Actual behavior
Making use of `curl -s https://get.docker.com/ | sh` when the overlay driver cannot be used doesn't allow docker service to be started.
### Steps to reproduce the behavior
After installing, I need to manually edit the containerd.service to remove the following line:
```
ExecStartPre=/sbin/modprobe overlay
```
Seems to be and issue with the latest docker. I just installed docker and it wouldn’t start, same issue as reported by yourself.
I Removed ExecStartPre=/sbin/modprobe overlay from containerd.service and sudo systemctl daemon-reload. Then rebooted (just restarting the services didn’t help, I’m guessing there is an order.)
Thanks Tom.