boot2docker

I would like to run a docker container that requires a lot of memory on a machine that doesn't have much RAM. I have been trying to increase the swap space available for the container to no avail. Here is the last command I tried: docker run -d -m 1000M --memory-swap=10000M --name=my_container my_image Following these tips on how to check memory metrics I found the following: $ boot2docker ssh docker@boot2docker:~$ cat /sys/fs/cgroup/memory/docker/35af5a072751c7af80ce7a255a01ab3c14b3ee0e3f15341f7bb22a777091c67b/memory.stat cache 454656 rss 65015808 rss_huge 29360128 mapped_file 208896

I'm trying to create a docker dev tools container for a devlopement environment on a windows host via docker toolbox but I have some trouble running the npm install command. It worked fine on a linux host but on the windows host I got the following error : npm ERR! Linux 4.1.13-boot2docker npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" npm ERR! node v5.5.0 npm ERR! npm v3.3.12 npm ERR! path /var/www/site/.npm/gulp/3.9.0/package.tgz.e87c24357cd6065ee71ce44c6f23673b npm ERR! code ETXTBSY npm ERR! errno -26 npm ERR! syscall rename npm ERR! ETXTBSY: text file is busy, rename '

When running a PostgreSQL database in a Docker container, the documentation for the official PostgreSQL Docker Image specifies that the administrator password should be set in an environmental variable like: docker run --name some-postgres -e POSTGRES_PASSWORD=mysecretpassword -d postgres For those that do not want to hard-code a plain-text password in their scripts, are there more secure options to consider? Injecting configuration settings as environment variables is the approach to application configuration recommended by the 12 factor app website. http://12factor.net/config Alternatively

I have a database docker container that is writing its data to another data-only container. The data-only container has a volume where it stores the data of the database. Is there a "docker" way of migrating this data-only container from one machine to another? I read about docker save and docker load but these commands save and load images, not containers. I want to be able to package the docker container along with its volumes and move it to another machine. Checkout the flocker project. Very interesting solution to this problem, using ZFS to snapshot and replicate the storage volume between

Is there a possibility to simply create a docker-machine that is non-boot2docker based (i.e., Ubuntu based) (which uses virtualbox driver)? I would like to have full-featured Linux distro running the docker daemon on my mac instead of Tiny Core Linux distro which is fast and lightweight but doesn't offer me all the debugging facilities I need. I know I can create it manually. I'm just wondering if there is a simple way such as docker-machine create is. You could take advantage of the --virtualbox-boot2docker-url option. This issue illustrates its usage (with an iso which is not a TinyCore one,