Update docker-ce to last supported Trusty release 馃拃 #11629
Conversation
This version of docker-ce is the last one that supports Trusty on a 3.x Linux Kernel [1]. I'm upgrading as we seem to be experiencing an issue with aufs (see below) on one of our machines. My investigation indicates that this may potentially be a bug in docker-ce that was fixed in 17.12.1 and 18.03 [2]. So I expect updating to 18.06.1 will resolve it - if not at least we're on a more recent version. ``` 17:45:53 driver "aufs" failed to remove root filesystem for 1689bc31da539840e42f29043cd62bd7ebab3da05d0d5094aafcaebb90ea1958: could not remove diff path for id 0be2d29298c44335f47beb6a20151f1fa1b9516a551f7a6beea00b62aa880faf: error preparing atomic delete: rename /var/lib/docker/aufs/diff/0be2d29298c44335f47beb6a20151f1fa1b9516a551f7a6beea00b62aa880faf /var/lib/docker/aufs/diff/0be2d29298c44335f47beb6a20151f1fa1b9516a551f7a6beea00b62aa880faf-removing: device or resource busy ``` [1]: https://docs.docker.com/engine/release-notes/18.06/ [2]: moby/moby#21704
There was a problem hiding this comment.
Nice. Will we be able to go for a newer version if we upgrade to a 4.x kernel I wonder?
We might do that in this card: https://trello.com/c/t9PmUATo/2878-workaround-or-fix-the-arp-caching-bug
It sounds like we can still go up a couple of patch releases to 18.06.2 as per their changelog of "Ubuntu 14.04 customers using a 3.13 kernel will need to upgrade to a supported Ubuntu 4.x kernel" for 18.06.2. But the bad news is that Trusty is an unsupported platform and I think they stopped pushing releases since 18.09 - could be that we could package it ourselves 馃槵 |
This version of docker-ce is the last one that supports Trusty on a
3.x Linux Kernel 1.
I'm upgrading as we seem to be experiencing an issue with aufs (see
below) on one of our machines. My investigation indicates that this may
potentially be a bug in docker-ce that was fixed in 17.12.1 and 18.03 2.
So I expect updating to 18.06.1 will resolve it - if not at least we're
on a more recent version.
I've been running this on integration for around an hour and it seems to have resolved the problem, as well as not introducing any new ones.