suxin1110/transmission repository overview

docker pull suxin1110/transmission 点击编辑在复制粘贴

docker run -d
--name=transmission
-e PUID=0
-e PGID=0
-e TZ=Asia/Shanghai
-e TRANSMISSION_WEB_HOME=/combustion-release/ #optional
-p 9091:9091
-p 51413:51413
-p 51413:51413/udp
-v /transmission/config:/config
-v /transmission/download:/downloads
-v /transmission/watch:/watch
suxin1110/transmission

Supported Architectures 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 and our announcement here.

Simply pulling 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:

Architecture Tag x86-64 amd64-latest arm64 arm64v8-latest armhf arm32v7-latest Usage Here are some example snippets to help you get started creating a container.

docker docker create
--name=transmission
-e PUID=1000
-e PGID=1000
-e TZ=Europe/London
-e TRANSMISSION_WEB_HOME=/combustion-release/ #optional
-p 9091:9091
-p 51413:51413
-p 51413:51413/udp
-v :/config
-v :/downloads
-v :/watch
--restart unless-stopped
linuxserver/transmission docker-compose Compatible with docker-compose v2 schemas.

---

version: "2" services: transmission: image: linuxserver/transmission container_name: transmission environment: - PUID=1000 - PGID=1000 - TZ=Europe/London - TRANSMISSION_WEB_HOME=/combustion-release/ #optional volumes: - :/config - :/downloads - :/watch ports: - 9091:9091 - 51413:51413 - 51413:51413/udp restart: unless-stopped Parameters Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate : 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.

Parameter Function -p 9091 WebUI -p 51413 Torrent Port TCP -p 51413/udp Torrent Port UDP -e PUID=1000 for UserID - see below for explanation -e PGID=1000 for GroupID - see below for explanation -e TZ=Europe/London Specify a timezone to use EG Europe/London. -e TRANSMISSION_WEB_HOME=/combustion-release/ Specify an alternative UI options are /combustion-release/ and /transmission-web-control/. -v /config Where transmission should store config files and logs. -v /downloads Local path for downloads. -v /watch Watch folder for torrent files. User / Group Identifiers When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

$ id username uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup) Application Setup Webui is on port 9091, the settings.json file in /config has extra settings not available in the webui. Stop the container before editing it or any changes won't be saved.

For users pulling an update and unable to access the webui setting you may need to set "rpc-host-whitelist-enabled": false, in /config/settings.json`

If you choose to use transmission-web-control as your default UI, just note that the origional Web UI will not be available to you despite the button being present.

Securing the webui with a username/password. this requires 3 settings to be changed in the settings.json file.

Make sure the container is stopped before editing these settings.

"rpc-authentication-required": true, - check this, the default is false, change to true.

"rpc-username": "transmission", substitute transmission for your chosen user name, this is just an example.

rpc-password will be a hash starting with {, replace everything including the { with your chosen password, keeping the quotes.

Transmission will convert it to a hash when you restart the container after making the above edits.

Updating Blocklists Automatically This requires "blocklist-enabled": true, to be set. By setting this to true, it is assumed you have also populated blocklist-url with a valid block list.

The automatic update is a shell script that downloads a blocklist from the url stored in the settings.json, gunzips it, and restarts the transmission daemon.

The automatic update will run once a day at 3am local server time.

Support Info Shell access whilst the container is running: docker exec -it transmission /bin/bash To monitor the logs of the container in realtime: docker logs -f transmission container version number docker inspect -f '{{ index .Config.Labels "build_version" }}' transmission image version number docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/transmission Updating Info Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Run/Create Update the image: docker pull linuxserver/transmission Stop the running container: docker stop transmission Delete the container: docker rm transmission 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 transmission You can also remove the old dangling images: docker image prune Via Taisun auto-updater (especially useful 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 shot: docker run --rm
-v /var/run/docker.sock:/var/run/docker.sock taisun/updater
--oneshot transmission 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 transmission Let compose update all containers as necessary: docker-compose up -d or update a single container: docker-compose up -d transmission You can also remove the old dangling images: docker image prune