# Problemas com Docker e kernel na Digital Ocean

**URL:** <https://meta.discourse.org/t/problems-with-docker-and-kernel-on-digital-ocean/60627>\
**Category:** Self-hosting\
**Created:** [Abril 8, 2017, 3:51am UTC](https://meta.discourse.org/t/problems-with-docker-and-kernel-on-digital-ocean/60627 "2017-04-08T03:51:22Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**Post date:** [Abril 8, 2017, 6:50am UTC](https://meta.discourse.org/t/problems-with-docker-and-kernel-on-digital-ocean/60627/21 "2017-04-08T06:50:15Z")

</div>

Not that I’m aware of.. this host does nothing but run Discourse.

What I have seen is weirdness running `apt-get dist-upgrade` and I’d told myself never to run that again.

I assume that apt-get upgrade shows newer versions of packages that don’t match the kernel, and.or the kernel is silently upgraded without me knowing, causing a mismatch in the extras. (or maybe the silent upgrade is something only Linode does.. I don’t know enough to know)

Regardless, I’ve come to distrust any docker upgrade because I can never tell if a bug in docker will cause an utter failure, or some other craziness.

Luckily, I have a forum that has very low use and can afford hours of downtime, so I use it as my guinea pig before I upgrade my three important ones.

The goal of this thread is to prevent such random failures.. I’m hopeful that ubuntu16 does that. So far, my guinea pig forum upgraded to ubuntu16 just fine.. my first real forum is busy rolling back since its boot volume was read-only after the upgrade.

---

_[View the full topic](https://meta.discourse.org/t/problems-with-docker-and-kernel-on-digital-ocean/60627)._