Update DigitalOcean images to 16.04

[ShockwaveNN]

No description provided.

[ShockwaveNN]

Tryed it today. Seems not working great.
It starts okay, but after you stop tests on some server and waiting for next test suite to run - it just hanges (on history page you can look it up)

Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-45-generic x86_64) 

* Documentation: https://help.ubuntu.com 
* Management: https://landscape.canonical.com 
* Support: https://ubuntu.com/advantage 

0 packages can be updated. 
0 updates are security updates. 


Using default tag: latest 
Pulling repository docker.io/onlyofficetestingrobot/nct-at-testing-node 

And test stops. After that next test can started okay, but may not.

It runner terminal output there is errors like this:

Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-45-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

0 packages can be updated.
0 updates are security updates.


8a23dc791c57
Pseudo-terminal will not be allocated because stdin is not a terminal.
"docker rm" requires at least 1 argument(s).
See 'docker rm --help'.

Usage:  docker rm [OPTIONS] CONTAINER [CONTAINER...]

Remove one or more containers
Error: image onlyofficetestingrobot/nct-at-testing-node:latest not found
docker: Error response from daemon: containerd: container did not start before the specified timeout.
Error response from daemon: Driver aufs failed to remove root filesystem d69407692716076f727659827b4bb744bc2b442b24bc235f702a2d554f47ac0d: aufs: unmount error after retries: /var/lib/$
ocker/aufs/mnt/3f6eecda36dcf14805d175b9b2ec175c4922e345b8585722547b5a2b714d3f50: device or resource busy
Pseudo-terminal will not be allocated because stdin is not a terminal.
"docker rm" requires at least 1 argument(s).
See 'docker rm --help'.

Usage:  docker rm [OPTIONS] CONTAINER [CONTAINER...]

Remove one or more containers
Error: image onlyofficetestingrobot/nct-at-testing-node:latest not found
docker: Error response from daemon: containerd: container did not start before the specified timeout.
Error response from daemon: Driver aufs failed to remove root filesystem ab27c7ff9986c333a7c3b19b26f0c2610be7746f6c88f10879ce5fed72260f41: aufs: unmount error after retries: /var/lib/d
ocker/aufs/mnt/00a0e2d0b96e1f862e2a10634c0d4742f0ba9778e69c6907ffaf4d7fb74e0cd2: device or resource busy
Pseudo-terminal will not be allocated because stdin is not a terminal.
"docker rm" requires at least 1 argument(s).
See 'docker rm --help'.

Seems those aufs related problems are docker bugs
See moby/moby#21704 and moby/moby#18509
Possible solution - not use aufs.

[ShockwaveNN]

If using overlay2 storage driver error almost the same:

Handler for POST /v1.24/containers/25c745cdd531937382384f0c6a3a1e2c568d140a47b0f81466f5a5663d06ba75/start returned error: containerd: container did not start before the specified timeout

Possible reason - do not use -rm flag in docker run

[ShockwaveNN]

Same error for devicemapper

[ShockwaveNN]

Removing --rm flag not helper either

[ShockwaveNN]

Replacing Process.kill('KILL', @ssh_pid) on Process.kill('TERM', @ssh_pid) not helped.

[ShockwaveNN]

Possible workaround - moby/moby#22260 (comment) not helped

[ShockwaveNN]

service docker restart not helped either

[ShockwaveNN]

Found the reason.
Mounting /mnt/data_share using sudo mount -a inside docker cause all that stuff.
Need to mount this on docker image while creating it, but not inside docker.
And only send volume using standart docker flags.

Also - you cannot delete privileged flag in docker run - missing it causing troubles in starting chrome