Ghcr io linux server base image alpine

The LinuxServer.io team brings you another container release featuring:

regular and timely application updates
easy user mappings (PGID, PUID)
custom base image with s6 overlay
weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
regular security updates

Blog — all the things you can do with our containers including How-To guides, opinions and much more!
Discord — realtime support / chat with the community and the team.
Discourse — post on our community forum.
Fleet — an online web interface which displays all of our maintained images.
GitHub — view the source for all of our repositories.
Open Collective — please consider helping us by either donating or contributing to our budget

Transmission is designed for easy, powerful use. Transmission has the features you want from a BitTorrent client: encryption, a web interface, peer exchange, magnet links, DHT, µTP, UPnP and NAT-PMP port forwarding, webseed support, watch directories, tracker editing, global and per-torrent speed limits, and more.

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

Architecture	Tag
x86-64	amd64-latest
arm64	arm64v8-latest
armhf	arm32v7-latest

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.

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.

Use the USER and PASS variables in docker run/create/compose to set authentication. Do not manually edit the settings.json to input user/pass, otherwise transmission cannot be stopped cleanly by the s6 supervisor.

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.

Use WHITELIST to enable a list of ip as whitelist. This enable support for rpc-whitelist . When WHITELIST is empty support for whitelist is disabled.

Use HOST_WHITELIST to enable an list of dns names as host-whitelist. This enable support for rpc-host-whitelist . When HOST_WHITELIST is empty support for host-whitelist is disabled.

Here are some example snippets to help you get started creating a container.

:/watch ports: — 9091:9091 — 51413:51413 — 51413:51413/udp restart: unless-stopped «>

:/watch \ —restart unless-stopped \ lscr.io/linuxserver/transmission «>

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/ , /transmission-web-control/ , /kettu/ and /flood-for-transmission/ .
-e USER=username	Specify an optional username for the interface
-e PASS=password	Specify an optional password for the interface
-e WHITELIST=iplist	Specify an optional list of comma separated ip whitelist. Fill rpc-whitelist setting.
-e HOST_WHITELIST=dnsnane list	Specify an optional list of comma separated dns name whitelist. Fill rpc-host-whitelist setting.
-v /config	Where transmission should store config files and logs.
-v /downloads	Local path for downloads.
-v /watch	Watch folder for torrent files.

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__ .

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it’s value it does not add. Please read up here before asking for support.

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:

We publish various 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.

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" >>’ lscr.io/linuxserver/transmission

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 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

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)
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:

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.

Image Update Notifications — Diun (Docker Image Update Notifier)

We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

If you want to make local modifications to these images for development purposes or just to customize the logic:

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

Источник

Building and maintaining community images

We are a group of like-minded enthusiasts from across the world who build and maintain the largest collection of Docker images on the web, and at our core are the principles behind Free and Open Source Software. Our primary goal is to provide easy-to-use and streamlined Docker images with clear and concise documentation.

A worldwide userbase

Our commitment is to the community and our users. Over the years, we have worked hard to build a name that resonates with home server enthusiasts and newcomers. Our images are for everyone, and always will be. We would like to thank everyone who has used our images and helped us achieve such a milestone.

Standardised Images

Our images are built from the same base, which we have uniquely curated. By using s6-overlay, each of our base images are highly extendable, making them configurable for practically any application. This standardization not only provides uniformity; it also saves our users bandwidth and storage by having each of our images share their base layers.

Regular Updates

Our build pipeline has been completely redesigned and now provides our users with fast and effective updates for our images. When the upstream applications or application dependencies are updated, our images will automatically rebuild. This mechanism ensures our images remain as up-to-date as possible. Our new tagging system also provides users with clearer indications as to which application version a particular build encapsulates.

First-class Documentation

It is our belief that with a first-class fleet of images comes a first-class set of documentation. All of our images come with clear and thorough set-up guides. These can be found either on GitHub or our dedicated Documentation space. Further guides and opinion pieces can also be found on our blog.

Support

Our community is ever-expanding, and as such requires the best possible support when using our images. We provide first-hand support via our Discord server, as well as our Discourse forum. Whether new to LinuxServer, or a returning veteran there will always be someone available from the team, or the community itself to help you through any issues.

Источник