If you are new to Docker or this application our issue tracker is **ONLY** used for reporting bugs or requesting features. Please use [our discord server](https://discord.gg/YWrKVTn) for general support.
<!--- If you are new to Docker or this application our issue tracker is**ONLY** used for reporting bugs or requesting features. Please use [our discord server](https://discord.gg/YWrKVTn) for general support. --->
<!--- If this acts as a feature request please ask yourself if this modification is something the whole userbase will benefit from --->
<!--- If this is a specific change for corner case functionality or plugins please look at making a Docker Mod or local script https://blog.linuxserver.io/2019/09/14/customizing-our-containers/ -->
<!--- Provide a general summary of the issue in the Title above -->
@ -25,6 +28,7 @@ If you are new to Docker or this application our issue tracker is **ONLY** used
**OS:**
**CPU architecture:** x86_64/arm32/arm64
**How docker service was installed:**
<!--- ie. from the official docker repo, from the distro repo, nas OS provided, etc. -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
## Command used to create docker container (run/create/compose/screenshot)
We welcome all PR’s though this doesn’t guarantee it will be accepted.
- [ ] I have read the [contributing](https://github.com/linuxserver/docker-ubooquity/blob/master/.github/CONTRIBUTING.md) guideline and understand that I have made the correct modifications
------------------------------
<!--- We welcome all PR’s though this doesn’t guarantee it will be accepted. -->
issue-message:'Thanks for opening your first issue here! Be sure to follow the [issue template](https://github.com/linuxserver/docker-ubooquity/.github/ISSUE_TEMPLATE.md)!'
pr-message:'Thanks for opening this pull request! Be sure to follow the [pull request template](https://github.com/linuxserver/docker-ubooquity/.github/PULL_REQUEST_TEMPLATE.md)!'
issue-message:'Thanks for opening your first issue here! Be sure to follow the [issue template](https://github.com/linuxserver/docker-ubooquity/blob/master/.github/ISSUE_TEMPLATE.md)!'
pr-message:'Thanks for opening this pull request! Be sure to follow the [pull request template](https://github.com/linuxserver/docker-ubooquity/blob/master/.github/PULL_REQUEST_TEMPLATE.md)!'
[](https://blog.linuxserver.io "all the things you can do with our containers including How-To guides, opinions and much more!")
@ -58,31 +61,11 @@ The architectures supported by this image are:
Here are some example snippets to help you get started creating a container.
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
@ -175,9 +178,9 @@ If no value is set it will default to 512MB.
## Docker Mods
[](https://mods.linuxserver.io/?mod=ubooquity "view available mods for this container.")
[](https://mods.linuxserver.io/?mod=ubooquity "view available mods for this container.") [](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) can be accessed via the dynamic badge above.
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
## Support Info
@ -195,14 +198,6 @@ Most of our images are static, versioned, and require an image update and contai
Below are the instructions for updating containers:
### Via Docker Run/Create
* Update the image: `docker pull linuxserver/ubooquity`
* Stop the running container: `docker stop ubooquity`
* Delete the container: `docker rm ubooquity`
* Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)
* Start the new container: `docker start ubooquity`
* You can also remove the old dangling images: `docker image prune`
### Via Docker Compose
* Update all images: `docker-compose pull`
* or update a single image: `docker-compose pull ubooquity`
@ -210,7 +205,14 @@ Below are the instructions for updating containers:
* or update a single container: `docker-compose up -d ubooquity`
* You can also remove the old dangling images: `docker image prune`
### Via Watchtower auto-updater (especially useful if you don't remember the original parameters)
### Via Docker Run
* Update the image: `docker pull linuxserver/ubooquity`
* Stop the running container: `docker stop ubooquity`
* Delete the container: `docker rm ubooquity`
* Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)
* You can also remove the old dangling images: `docker image prune`
### Via Watchtower auto-updater (only use if you don't remember the original parameters)
* Pull the latest image at its tag and replace it with the same env variables in one run:
```
docker run --rm \
@ -218,10 +220,12 @@ Below are the instructions for updating containers:
containrrr/watchtower \
--run-once ubooquity
```
* You can also remove the old dangling images: `docker image prune`
**Note:** We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
**Note:** We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using [Docker Compose](https://docs.linuxserver.io/general/docker-compose).
* You can also remove the old dangling images: `docker image prune`
* We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
LinuxServer-CI
4 years ago