In your second (working) example, I see you run "service docker stop"
before deleting the contents of "/var/lib/docker" but I do not see that
in your first example, which would definitely explain the behavior you
see ("service docker start" would be a no-op because Docker's already
running, and you've just yanked out all the data from underneath it, so
it's not very surprising that it sees errors trying to access said
data).-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950751 Title: docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1950751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
