本站面向开发者与科研用户,提供开源镜像的搜索和下载加速服务。
所有镜像均来源于原始开源仓库,本站不存储、不修改、不传播任何镜像内容。

sickrage Docker 镜像下载 - 轩辕镜像

sickrage 镜像详细信息和使用指南

sickrage 镜像标签列表和版本信息

sickrage 镜像拉取命令和加速下载

sickrage 镜像使用说明和配置指南

Docker 镜像加速服务 - 轩辕镜像平台

国内开发者首选的 Docker 镜像加速平台

极速拉取 Docker 镜像服务

相关 Docker 镜像推荐

热门 Docker 镜像下载

sickrage
linuxserver/sickrage

sickrage 镜像详细信息

sickrage 镜像标签列表

sickrage 镜像使用说明

sickrage 镜像拉取命令

Docker 镜像加速服务

轩辕镜像平台优势

镜像下载指南

相关 Docker 镜像推荐

A SickRage container, brought to you by LinuxServer.io.
144 收藏0 次下载activelinuxserver镜像

sickrage 镜像详细说明

sickrage 使用指南

sickrage 配置说明

sickrage 官方文档

undefined![linuxserver.io]([***]

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

Find us at:

  • *** - realtime support / chat with the community and the team.
  • IRC - on freenode at #linuxserver.io. Our primary support channel is ***.
  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!

linuxserver/sickrage

![]([] !Docker Pulls !Docker Stars ![Build Status]([] ![]([***]

Sickrage has been deprecated. Please use *** instead

![sickrage]([***]

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

ArchitectureTag
x86-64amd64-latest
arm64arm64v8-latest
armhfarm32v7-latest

Usage

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

docker

docker create \
  --name=sickrage \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 8081:8081 \
  -v /path/to/appdata/config:/config \
  -v /path/to/downloads:/downloads \
  -v /path/to/tv/shows:/tv \
  --restart unless-stopped \
  linuxserver/sickrage

docker-compose

Compatible with docker-compose v2 schemas.

---
version: "2"
services:
  sickrage:
    image: linuxserver/sickrage
    container_name: sickrage
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - /path/to/appdata/config:/config
      - /path/to/downloads:/downloads
      - /path/to/tv/shows:/tv
    ports:
      - 8081:8081
    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 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.

ParameterFunction
-p 8081Application WebUI
-e PUID=1000for UserID - see below for explanation
-e PGID=1000for GroupID - see below for explanation
-e TZ=Europe/LondonSpecify a timezone to use EG Europe/London.
-v /configConfiguration files.
-v /downloadsISOs.
-v /tvTV library directory.

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

Web interface is at your ip:8081 , set paths for downloads, tv-shows to match docker mappings via the webui.

Support Info

  • Shell access whilst the container is running: docker exec -it sickrage /bin/bash
  • To monitor the logs of the container in realtime: docker logs -f sickrage
  • container version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' sickrage
  • image version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/sickrage

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/sickrage
  • Stop the running container: docker stop sickrage
  • Delete the container: docker rm sickrage
  • 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 sickrage
  • 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 sickrage
  • Let compose update all containers as necessary: docker-compose up -d
    • or update a single container: docker-compose up -d sickrage
  • 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)

  • Pull the latest image at its tag and replace it with the same env variables in one run:
    docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock \
    containrrr/watchtower \
    --run-once sickrage
    
  • You can also remove the old dangling images: docker image prune

Building locally

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

git clone [***]
cd docker-sickrage
docker build \
  --no-cache \
  --pull \
  -t linuxserver/sickrage:latest .

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

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 22.02.19: - Rebasing to alpine 3.9.
  • 16.01.19: - Add pipeline logic and multi arch.
  • 09.08.18: - Change repository to Sick-Rage
  • 17.08.18: - Rebase to alpine 3.8.
  • 20.03.18: - In lieu of a definite fix from SR, add nodejs package for use with torrentz and other sources.
  • 12.12.17: - Rebase to alpine 3.7.
  • 06.08.17: - Internal git pull instead of at runtime.
  • 25.05.17: - Rebase to alpine 3.6.
  • 07.02.17: - Rebase to alpine 3.5.
  • 14.10.16: - Add version layer information.
  • 30.09.16: - Fix umask.
  • 09.09.16: - Add layer badges to README.
  • 28.08.16: - Add badges to README.
  • 08.08.16: - Rebase to alpine linux.
  • 30.12.15: - Build later version of unrar from source, removed uneeded mako package.
  • 20.11.15: - Updated to new repo, by SickRage Team.
  • 15.10.15: - Initial Release.

轩辕镜像下载加速使用手册

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式

登录方式进行 Docker 镜像下载加速教程

通过 Docker 登录方式配置轩辕镜像加速服务,包含7个详细步骤

Linux Docker 镜像下载加速教程

在 Linux 系统上配置轩辕镜像源,支持主流发行版

Windows/Mac Docker 镜像下载加速教程

在 Docker Desktop 中配置轩辕镜像加速,适用于桌面系统

Docker Compose 镜像下载加速教程

在 Docker Compose 中使用轩辕镜像加速,支持容器编排

K8s containerd 镜像下载加速教程

在 k8s 中配置 containerd 使用轩辕镜像加速

宝塔面板 Docker 镜像下载加速教程

在宝塔面板中配置轩辕镜像加速,提升服务器管理效率

群晖 NAS Docker 镜像下载加速教程

在 Synology 群晖NAS系统中配置轩辕镜像加速

飞牛fnOS Docker 镜像下载加速教程

在飞牛fnOS系统中配置轩辕镜像加速

极空间 NAS Docker 镜像下载加速教程

在极空间NAS中配置轩辕镜像加速

爱快路由 ikuai Docker 镜像下载加速教程

在爱快ikuai系统中配置轩辕镜像加速

绿联 NAS Docker 镜像下载加速教程

在绿联NAS系统中配置轩辕镜像加速

威联通 NAS Docker 镜像下载加速教程

在威联通NAS系统中配置轩辕镜像加速

Podman Docker 镜像下载加速教程

在 Podman 中配置轩辕镜像加速,支持多系统

ghcr、Quay、nvcr、k8s、gcr 等仓库下载镜像加速教程

配置轩辕镜像加速9大主流镜像仓库,包含详细配置步骤

专属域名方式进行 Docker 镜像下载加速教程

无需登录即可使用轩辕镜像加速服务,更加便捷高效

需要其他帮助?请查看我们的 常见问题 官方QQ群: 13763429