# Docker broken on Ubuntu 16.04?

**URL:** <https://meta.discourse.org/t/docker-broken-on-ubuntu-16-04/138873>\
**Category:** Self-hosting\
**Created:** [January 16, 2020, 8:23pm UTC](https://meta.discourse.org/t/docker-broken-on-ubuntu-16-04/138873 "2020-01-16T20:23:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [January 16, 2020, 11:11pm UTC](https://meta.discourse.org/t/docker-broken-on-ubuntu-16-04/138873/2 "2020-01-16T23:11:18Z")

</div>

Have you rebooted? I’ve had trouble with Docker if I’ve done an upgrade and didn’t reboot.

Yeah. That’s scary-sounding. I know that I have sites on 16.04 and know that I haven’t done anything with `runc`.

If you’re concerned about down time and you’re on Digital Ocean, you might just

1. spin up a new droplet with 18.04 and do a clean install.
2. Get an floating IP, point it at the old server, and point DNS there.
3. Put the old forum in read-only
4. back up
5. restore to the new server
6. re-point the floating IP to the new server.

You’ll have no down time and just the read-only time it takes to back up and restore. You can practice a time or two before you do the read-only bit. You could also `rsync` uploads rather than including them in the backup, so you’d need to backup/restore just the database.

You’d probably want to pull over your existing let’s encrypt certs too, though, or, I think, you’ll have to rebuild to get them.

---

_[View the full topic](https://meta.discourse.org/t/docker-broken-on-ubuntu-16-04/138873)._