mirror of
				https://github.com/linuxserver/docker-transmission.git
				synced 2025-10-31 17:05:48 +01:00 
			
		
		
		
	Bot Updating Templated Files
This commit is contained in:
		
							
								
								
									
										13
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										13
									
								
								README.md
									
									
									
									
									
								
							| @@ -33,6 +33,7 @@ Find us at: | ||||
| [](https://github.com/linuxserver/docker-transmission/releases) | ||||
| [](https://github.com/linuxserver/docker-transmission/packages) | ||||
| [](https://gitlab.com/linuxserver.io/docker-transmission/container_registry) | ||||
| [](https://quay.io/repository/linuxserver.io/transmission) | ||||
| [](https://hub.docker.com/r/linuxserver/transmission) | ||||
| [](https://hub.docker.com/r/linuxserver/transmission) | ||||
| [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-transmission/job/master/) | ||||
| @@ -46,7 +47,7 @@ Find us at: | ||||
|  | ||||
| Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/). | ||||
|  | ||||
| Simply pulling `ghcr.io/linuxserver/transmission` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. | ||||
| Simply pulling `lscr.io/linuxserver/transmission` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. | ||||
|  | ||||
| The architectures supported by this image are: | ||||
|  | ||||
| @@ -91,7 +92,7 @@ Here are some example snippets to help you get started creating a container. | ||||
| version: "2.1" | ||||
| services: | ||||
|   transmission: | ||||
|     image: ghcr.io/linuxserver/transmission | ||||
|     image: lscr.io/linuxserver/transmission | ||||
|     container_name: transmission | ||||
|     environment: | ||||
|       - PUID=1000 | ||||
| @@ -133,7 +134,7 @@ docker run -d \ | ||||
|   -v <path to downloads>:/downloads \ | ||||
|   -v <path to watch folder>:/watch \ | ||||
|   --restart unless-stopped \ | ||||
|   ghcr.io/linuxserver/transmission | ||||
|   lscr.io/linuxserver/transmission | ||||
| ``` | ||||
|  | ||||
| ## Parameters | ||||
| @@ -200,7 +201,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to | ||||
| * container version number | ||||
|   * `docker inspect -f '{{ index .Config.Labels "build_version" }}' transmission` | ||||
| * image version number | ||||
|   * `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/transmission` | ||||
|   * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/transmission` | ||||
|  | ||||
| ## Updating Info | ||||
|  | ||||
| @@ -218,7 +219,7 @@ Below are the instructions for updating containers: | ||||
|  | ||||
| ### Via Docker Run | ||||
|  | ||||
| * Update the image: `docker pull ghcr.io/linuxserver/transmission` | ||||
| * Update the image: `docker pull lscr.io/linuxserver/transmission` | ||||
| * Stop the running container: `docker stop transmission` | ||||
| * Delete the container: `docker rm transmission` | ||||
| * 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) | ||||
| @@ -253,7 +254,7 @@ cd docker-transmission | ||||
| docker build \ | ||||
|   --no-cache \ | ||||
|   --pull \ | ||||
|   -t ghcr.io/linuxserver/transmission:latest . | ||||
|   -t lscr.io/linuxserver/transmission:latest . | ||||
| ``` | ||||
|  | ||||
| The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static` | ||||
|   | ||||
		Reference in New Issue
	
	Block a user