Is it possible to configure the Docker storage driver used by builds?

[ray-grointel]

We're using a custom Docker image for our shippable builds, and have had errors caused by the Docker AUFS storage driver's lack of support for some filesystem actions:

Renaming directories: Calling rename(2) for a directory is not fully supported on AUFS. It returns EXDEV (“cross-device link not permitted”), even when both of the source and the destination path are on a same AUFS layer, unless the directory has no children. Your application needs to be designed to handle EXDEV and fall back to a “copy and unlink” strategy.

We've seen this issue affect npm --global install commands, and raise "postgres permission denied" errors:

• Permission denied on SSL certificat Painted-Fox/docker-postgresql#30 (comment)
• UTC FATAL: could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied puntonim/docker-postgresql93#2 (comment)

Some solutions suggested include switching the Docker storage driver from AUFS to devicemapper:

• UTC FATAL: could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied puntonim/docker-postgresql93#2 (comment)

Is it possible to configure the Docker storage driver used by builds? https://docs.docker.com/storage/storagedriver/device-mapper-driver/#configure-docker-with-the-devicemapper-storage-driver

---

Example build: https://app.shippable.com/bitbucket/grointelligence/gro/runs/19351/1/console

[trriplejay]

Currently this is not a configuration option that we provide. I think if you were to utilize our BYON feature that you might be able to configure a node to use device mapper instead.