Description of problem:

A new docker container is created every time I reboot the machine for Dokku apps.

Output of the following commands

• dokku version:

v0.4.0

• dokku plugins:

 !     `plugins` is not a dokku command.
 !     See `dokku help` for a list of available commands.

• docker version:

Client:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   0a8c2e3
 Built:        Thu Sep 10 19:19:00 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   0a8c2e3
 Built:        Thu Sep 10 19:19:00 UTC 2015
 OS/Arch:      linux/amd64

• docker info:

Containers: 5
Images: 9
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 19
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-25-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 993.2 MiB
Name: dokku
ID: F5XJ:RPWM:PSSQ:OY32:XEHY:TQ6C:YYJQ:K4WG:O4SP:QUA7:63LM:JNHQ
WARNING: No swap limit support

• uname -a:

Linux dokku 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Environment details (AWS, VirtualBox, physical, etc.):

Running Dokku on a clean VirtualBox machine with a clean Ubuntu Server 14.04.3 LTS install.
How was dokku installed?:

$ history
    1  sudo apt-get update
    2  sudo apt-get upgrade
    3  wget https://raw.github.com/progrium/dokku/v0.4.0/bootstrap.sh
    4  sudo DOKKU_TAG=v0.4.0 bash bootstrap.sh
    5  sudo sshcommand acl-add dokku bob
        ...

How reproducible:
I just did this a second time to make sure it wasn't some mistake:

• Create a new virtual machine in VirtualBox.
• Install Ubuntu Server 14.04.3 LTS with OpenSSH server.
• Run commands above to update/upgrade and install dokku.
• Push NodeJS application to dokku@dokku.local:cycle-remote
• Check sudo docker ps and verify one container is running.
• sudo reboot
• Check sudo docker ps again and notice there are 2 containers running.

Actual Results:

More reboots results in more running containers!

Expected Results:

The same container that was initially started should be running after rebooting.

Additional info:

I did notice that no web-based installer was started nor was it available on http://dokku.local/. http://dokku.local/ only showed the default nginx page after installing Dokku.

Additionally after pushing my app to cycle-remote (or cycleremote) I couldn't access the app through http://cycle-remote.dokku.local/ or http://cycle-remote.dokku.local/. I noticed NO_VHOST was set to 1, so I used dokku config:unset cycle-remote NO_VHOST. This still did not bring up the mentioned urls. Only after issueing dokku domains:add cycle-remote cycle-remote.dokku.local did the url come up. I presume this is unrelated to the issue I'm submitting, but I thought I'd mention this.