Unofficial Linuxserver.io image, use issue tracker for potentional problems.
Aria2 is a lightweight multi-protocol & multi-source command-line download utility. It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink. aria2 can be manipulated via built-in JSON-RPC and XML-RPC interfaces.
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 lukasmrtvy/lsiobase-aria2-webui 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 |
Here are some example snippets to help you get started creating a container.
docker create \
--name=aria2 \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-p 4040:4040 \
-v </path/to/appdata/config>:/data/config \
-v </path/to/downloads>:/data/downloads \
-e WEBUI=aria \
--restart unless-stopped \
lukasmrtvy/lsiobase-aria2-webui
Compatible with docker-compose v2 schemas.
---
version: "2"
services:
aria2:
image: lukasmrtvy/lsiobase-aria2-webui
container_name: aria2
environment:
- PUID=1000
- PGID=1000
- WEBUI=aria
- TZ=Europe/London
volumes:
- </path/to/appdata/config>:/data/config
- </path/to/downloads>:/data/downloads
ports:
- 4040:4040
restart: unless-stopped
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.
| Parameter | Function |
|---|---|
-p 4040 | http gui |
-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 |
-v /data/config | aria2 Application Data. |
-v /data/downloads | Downloads Folder. |
-e CUSTOM_RPC_TOKEN | Optional. Specify custom RPC token vaule. |
-e CUSTOM_OVERRIDE_OPTIONS | Optional. Pass arguments to aria2 daemon |
-e SKIP_SSL=true | Optional. Disable HTTPS |
-e WEBUI=aria | Optional. Defaults to ariang |
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)
Access the webui at <your-ip>:443and setup connection to Aria2 RPC. for more information check out Aria2 WebUI.
You can use also custom clients with same connection string.
docker exec -it aria2 /bin/bashdocker logs -f aria2docker inspect -f '{{ index .Config.Labels "build_version" }}' aria2docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/aria2Most 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:
docker pull lukasmrtvy/lsiobase-aria2-webuidocker stop aria2docker rm aria2/config folder and settings will be preserved)docker start aria2docker image prunedocker-compose pull
docker-compose pull aria2docker-compose up -d
docker-compose up -d aria2docker image pruneContent type
Image
Digest
Size
27.5 MB
Last updated
almost 7 years ago
docker pull lukasmrtvy/lsiobase-aria2-webui