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.