Girish Ramakrishnan
bbef6c2bc2
When docker is not passed the --storage-driver option, it tries to auto detect the storage driver. Roughly: 1. If existing storage paths like /var/lib/docker/aufs exist, it will choose that driver. 2. It has a priority list of drivers to scan in order (driver.go) As it stands the ordering is aufs, btrfs and then devicemapper. 3. Docker will attempt to "init" each driver. aufs, for example, tests for insmod'ing aufs and also looks into /proc/filesystems. The fact that we installed aufs-tools and linux drivers (for aufs driver) was a programming error since we want docker to use devicemapper. However, what is curious is why docker still ended up choosing devicemapper despite having all aufs requirements (as we do not pass --storage-driver explicitly). The answer is that "apt-get install aufs-tool linux-image-* docker-engine" can install packages in any order! This means there is a race on how docker chooses the storage engine. In most cases, since linux-image-* is a big package, docker gets to install first and ends up using devicemapper since aufs module is not found yet. For some people, linux-image-* possibly installs first and thus docker chooses aufs! Mystery solved. Part of #183
Cloudron
Cloudron is the best way to run apps on your server.
Web applications like email, contacts, blog, chat are the backbone of the modern internet. Yet, we live in a world where hosting these essential applications is a complex task.
We are building the ultimate platform for self-hosting web apps. The Cloudron allows anyone to effortlessly host web applications on their server on their own terms.
Support us on
or pay us a coffee
Features
-
Single click install for apps. Check out the App Store.
-
Per-app encrypted backups and restores.
-
App updates delivered via the App Store.
-
Secure - Cloudron manages the firewall. All apps are secured with HTTPS. Certificates are installed and renewed automatically.
-
Centralized User & Group management. Control who can access which app.
-
Single Sign On. Use same credentials across all apps.
-
Automatic updates for the Cloudron platform.
-
Trivially migrate to another server keeping your apps and data (for example, switch your infrastructure provider or move to a bigger server).
-
Comprehensive REST API.
-
CLI to configure apps.
-
Alerts, audit logs, graphs, dns management ... and much more
Demo
Try our demo at https://my-demo.cloudron.me (username: cloudron password: cloudron).
Installing
You can install the Cloudron platform on your own server or get a managed server from cloudron.io.
Documentation
Related repos
The base image repo is the parent image of all the containers in the Cloudron.
The graphite repo contains the graphite code that collects metrics for graphs.
The addons are located in separate repositories