Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with VPS provisionning #4

Open
btoueg opened this issue Nov 29, 2015 · 1 comment
Open

Issue with VPS provisionning #4

btoueg opened this issue Nov 29, 2015 · 1 comment

Comments

@btoueg
Copy link
Contributor

btoueg commented Nov 29, 2015

I could not fix my OVH Docker 15.04 VPS Cloud with https://github.com/PEM--/devops-tuts/blob/master/provisioning.sh#L4

Here is what I get:

root@prod:~# /usr/bin/docker daemon -H tcp://0.0.0.0:2376 \
                                -H unix:///var/run/docker.sock \
                                --storage-driver aufs \
                                --tlsverify \
                                --tlscacert /etc/docker/ca.pem \
                                --tlscert /etc/docker/server.pem \
                                --tlskey /etc/docker/server-key.pem \
                                --label provider=generic \
                                --dns 8.8.8.8 --dns 8.8.4.4
FATA[0000] Error starting daemon: error initializing graphdriver: driver not supported

I found that omitting --storage-driver aufs fixes the issue, though I don't understand the consequence of removing this option, nor do I understand why I don't get this error on my Vagrant dev and pre.

Here is my VPS: Linux prod 3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16 17:15:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Here is my Vagrant: Linux dev 3.19.0-33-generic #38-Ubuntu SMP Fri Nov 6 18:18:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

@PEM--
Copy link
Owner

PEM-- commented Nov 29, 2015

It seems related to this: moby/moby#15651

Apparently during a security upgrade, the driver aufs is no longer available. The aufs driver is the oldest driver for unifying access to the file system. Other drivers may be less optimized which could result in less efficient footprint and startup time.

That should not be a major issue if you are not deploying a PaaS where you will launch dedicated containers each time a new account is created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants