Refer to our Support Page for our Support Channels and Tutorials we have found users have made with DockSTARTer!
For new installs the default
~/.config/appdata. Users who ran DockSTARTer before this location became the default may have
~/.docker/config, and we advise relocating.
If you'd like to move your existing config to a new location you can do the following:
~/. docker/compose/.env (in any text editor) and set
(You can choose anywhere to save configs, this example only shows the default location).
Then run the following commands:
ds -u ds -c down # Move your current config folder to the new location, ex: sudo mv ~/.docker/config ~/.config/appdata ds -c
That's it! Your containers should fire right back up as if nothing has changed. If you have any issues feel free to ask for help in
Ouroboros or Watchtower Enabled By Default
This tool is extremely useful for people getting used to running Docker. Its official documentation should explain why but you can disable it if you want.
Ouroboros will monitor (all or specified) running Docker containers and update them to the (latest or tagged) available image in the remote registry. Watchtower will pull down your new image, gracefully shut down your existing container and restart it with the same options that were used when it was deployed initially.
In short, Ouroboros and Watchtower do the same thing: keeps your containers up to date.
When I run
ds -c and it recreates some of the containers, is that because they have had updates from last run
With Ouroboros (or Watchtower) your containers will be updated to the latest images automatically. However, docker-compose has no idea what's updated, docker-compose keeps track of things independently from Ouroboros/Watchtower. Additionally, Ouroboros/Watchtower doesn't update docker-compose's method of tracking, therefore, compose might "recreate" containers that are already up to date. This is not a big deal it's basically just a container restart, and you were planning on running
ds -c expecting some kind of updates anyway.
General troubleshooting help
You can see the (quite helpful) logs of each container with the
docker logs <appname> command.
Additionally, you can also use Dozzle if you prefer to view logs using your browser.
Creating network "compose_default" with the default driver ERROR: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network
This error can occur if your connected to a VPN while setting up the containers. Simply temporarily disconnect your VPN connection until the containers have been created and then reconnect again.
Starting containers and getting the following or a similar error message: "listen udp 0.0.0.0:5353: bind: address already in use"
As you could probably guess this means an application (most likely Plex) is trying to use a port that is already in use. You can check which application it is with:
sudo lsof -i :<myport>
So in this example it would be:
sudo lsof -i :5353
which will show you that Google Chrome is using the port you need. In this case you could just close Chrome, but there may be applications you need to uninstall for this to work properly.
We have had a recent influx of users asking for assistance in how to make OMV work with DockSTARTer (DS). DS staff have tested and confirmed the following installation method on OMV version 5.5.
If you are a Linux newbie, we strongly discourage this approach because of all the issues that might arise with how OMV is built, and troubleshooting issues in OMV can be a pain. However, if you feel comfortable with Linux and want to continue down this route you will need to ensure the following:
You have installed all the necessary updates that are pending in your system.
You have set a DNS server in your Web GUI.
You have created a user with a home directory outside of the system disk that has
sshpermissions. See below in how to do that.
You have a secondary disk other than the system drive mounted and formatted to anything other than NTFS.
We recommend you set up a specific "Shared Folder" for your home directory.
appdatadirectory should only be used to store container configurations, not home directories.
SSH to your host as root. You will need to edit a system config file in order to avoid issues in the future. Run the following command (you can use your favorite text editor for this portion):
We are looking for the following line:
The part you care about is the
noexec bit. You will need to remove that string. Save the file and per OMV documentation you need to run
omv-salt deploy run fstab. To verify that the
noexec flag was removed from your drive run
cat /proc/mounts and find your drive on the list. You can also run
cat /proc/mounts | grep partial_drive_name. If the
noexec flag is present, you skipped a step.
We are now going to work on creating the directories for DS to use. You will need to create 4 shared folders and allow "Everyone read/write". The 4 directories will be called
The last directory should be where you store your user directories and you should not be using the system disk for that. If you do not know how to create a user and assign it a home directory; look up the OMV documentation as that is outside of the scope of this guide.
Once the above requirements have been met, you will need to SSH to your OMV host using the account you created. First make sure your home directory was set up correctly by typing
cd ~. This shouldn't return an error, if it does read over the OMV documentation in how to properly create a user with a home directory. If no error occurs, run the following commands:
sudo apt-get install curl git
bash -c "$(curl -fsSL https://get.dockstarter.com)"
After the reboot is complete, SSH back to your host using your user account and run
ds, type your password and select "Configuration". Select "Set Global Variables" and select "No" on the next prompt. The only thing we recommend changing is the
Use System 100. On the next screen, please take note of the path that starts with
/srv/dev-disk-by-label-XXX. You are going to want to remember this path to set your
downloads folder to that path, for instance: