I performed a 'docker version' command and received the following results:

 

Client version: 1.4.1

Client API version: 1.16

Go version (client): go1.3.3

Git commit (client): c2ff8a36

OS/Arch (client): linux/amd64

Server version: 1.4.1

Server API version: 1.16

Go version (server): go1.3.3

Git commit (server): c2ff8a36

 

On the Docker site, I see there is a newer version out (from the release notes):

 

Version 1.5.0

(2015-02-03)

 

Is it possible to update manually to the new version or is this ill advised?

there's no package manager in unraid, so there's no "easy" way to do it.

Man, that is kind of a bummer.  I wonder what the reason behind that is?

If you go through the bilge forum, you will be able to find tons and tons of arguments back and forth about that.

Man, that is kind of a bummer.  I wonder what the reason behind that is?

The main reason is that unRAID OS uses a RAM filesystem, which means that most of the operating system folders exist only in RAM. Each time you boot, unRAID unpacks the OS from the bzimage/bzroot files in the unRAID distribution files. No changes to the OS can survive a reboot. This is not uncommon for an "embedded" device.

 

The debate is mostly about whether or not unRAID OS should be a RAMfs or not. Limetech says yes.

 

Hmm, yes I can see the argument.  Last time I can think I had a ram based OS like this was with the Amiga OS in the late 80s/early 90s and it's "ramdisk"/rd0. 

Hmm, yes I can see the argument.  Last time I can think I had a ram based OS like this was with the Amiga OS in the late 80s/early 90s and it's "ramdisk"/rd0. 

You probably use some "devices" that do it like that, routers for instance.