docker. and messages.log files fill up the first partition on a busy worker

[spanditcaa]

Expected behavior

log files don't fill up the drive

Actual behavior

log files fill up the drive

Steps to reproduce the behavior

Hi @ddebroy - related to #31, @jparkerCAA and I noticed notice that the docker and messages logs on each worker are being written to the small 30gb partition on each host. Once we enabled our continuous integration pipeline, we filled up the drive within 2 days. It would be nice to specify a maximum file size for the various logs and they should be relocated to the much larger secondary partition on each host.

[gscott]

@ddebroy any word on this or #31? It will need to be fixed in your ARM template I assume.

[ddebroy]

@gscott this as well as https://github.com/docker/for-azure/issues/31 is fixed in the 17.06.2-ee-3 version of the template and the VHD it references. The template is in the process of being certified by Azure Marketplace but you can test a fresh deployment right now using https://download.docker.com/azure/17.06/17.06.2/Docker-DDC.tmpl which incorporates the above fixes.

Please note that the upgrading to this version from a previous version with UCP/DTR/EE is not supported at the moment but will be supported soon.

[FrenchBen]

@gscott The link is used on upgrades following the proper upgrade steps detailed here: https://docs.docker.com/docker-for-azure/upgrade/

The template is currently going through the Azure Marketplace approval process

[spanditcaa]

By private, you mean posted to a public github repository's issues ?

[FrenchBen]

@spanditcaa precisely 😅 - edited for clarity