make the same resource available through dual-stack IPv4 and IPv6

Since you will need 2 configurations, 2 ingresses and are charged 2 times, I would not agree with the term dual-stack. I would call that double-stack.

Currently I am using both @uifabric/utilities and @uifabric/styling in my imports and package.json, even though @uifabric/utilities is already a dependency of @uifabric/styling.

The following functions / types in particular are not reexported in @uifabric/styling:

• IStyleFunctionOrObject
• IStyleFunction
• classNamesFunction
• styled

The license text is currently not provided with the npm bundle. In order to allow automation tools like license-webpack-plugin to pick it up, it should be included there. Also the license states: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. This includes the npm registry.

The license text is currently not provided with the npm bundle. In order to allow automation tools like license-webpack-plugin to pick it up, it should be included there. Also the license states: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. This includes the npm registry.

The license text is currently not provided with the npm bundle. In order to allow automation tools like license-webpack-plugin to pick it up, it should be included there. Also the license states: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. This includes the npm registry.

The license text is currently not provided with the npm bundle. In order to allow automation tools like license-webpack-plugin to pick it up, it should be included there. Also the license states: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. This includes the npm registry.

Just for the future readers here. I discovered that using host networking and a static route configuration was not necessary. What I did was to create a macvlan and let the jellyfin container be in both macvlan and traefik vlan. This simplifies the whole setup.

version: "3.8"
services:
    traefik:
        image: traefik
        restart: always
        networks:
            - traefik
        command:
            - "--providers.docker=true"
            - "--providers.docker.exposedByDefault=false"
            - "--entryPoints.web.address=:80"
            - "--entryPoints.websecure.address=:443"
        ports:
            - 80:80
            - 443:443
        volumes:
            - /var/run/docker.sock:/var/run/docker.sock:ro
        labels:
            - "traefik.http.middlewares.redirect-to-https.redirectscheme.scheme=https"
            - "traefik.http.middlewares.redirect-to-https.redirectscheme.permanent=true"
    jellyfin:
        image: jellyfin/jellyfin
        restart: unless-stopped
        user: 1000:1000
        networks:
            - vlan3
            - traefik
        volumes:
            - jellyfin_config:/config
            - jellyfin_cache:/cache
            - media:/media:ro
        labels:
            - "traefik.enable=true"
            - "traefik.http.routers.jellyfin.rule=Host(`jellyfin.${DOMAIN}`)"
            - "traefik.http.routers.jellyfin.entrypoints=web"
            - "traefik.http.routers.jellyfin.middlewares=redirect-to-https"
            - "traefik.http.routers.jellyfinsecure.rule=Host(`jellyfin.${DOMAIN}`)"
            - "traefik.http.routers.jellyfinsecure.entrypoints=websecure"
            - "traefik.http.routers.jellyfinsecure.tls=true"
            - "traefik.http.services.jellyfinsecure.loadbalancer.server.port=8096"
networks:
    traefik:
    macvlan:
        driver: macvlan
        driver_opts:
            parent: eth0 #replace with your host interface / vlan to use
        ipam:
            config:
                - subnet: 10.0.0.0/16 #docker will assign ip addresses from this range, check your DHCP configuration
volumes:
    jellyfin_config:
        driver: local
    jellyfin_cache:
        driver: local
    media:
        driver: local

In general I am not able to persist custom CA configuration.

Expected Behavior

When I change CA certificate or path inside the UI, that change should be persisted in /config or additional required mounts points should be documented

Current Behavior

I need to configure after each container start

Steps to Reproduce

1. Start container
2. Start a torrent using an untrusted announce URL and get it erroring
3. Change advanced values to include custom CA cert (pem)
4. Update Tracker (should resolve the error)
5. Restart container

Environment

OS: debian CPU architecture: x86_64 How docker service was installed:
Though repository, docker-compose prebuilt binary

Command used to create docker container (run/create/compose/screenshot)

rutorrent:
        image: linuxserver/rutorrent:v3.10-ls90
        restart: unless-stopped
        environment:
            - PUID=1000
            - PGID=1000
            - TZ=Europe/Berlin
        ports:
            - 51413:51413
            - 51413:51413/udp
        volumes:
            - ./certs:/certs
            - rutorrent_config:/config
            - rutorrent_downloads:/downloads

Nevermind, most probably the issue is, that ruTorrent / rtorrent does not persist those settings at all. The solution is probably, to fix stuff in /etc/ssl/certs, which libcurl uses by default without needing to specify --cacert or --capath arguments.

In general I am not able to persist custom CA configuration.

Expected Behavior

When I change CA certificate or path inside the UI, that change should be persisted in /config or additional required mounts points should be documented

Current Behavior

I need to configure after each container start

Steps to Reproduce

1. Start container
2. Start a torrent using an untrusted announce URL and get it erroring
3. Change advanced values to include custom CA cert (pem)
4. Update Tracker (should resolve the error)
5. Restart container

Environment

OS: debian CPU architecture: x86_64 How docker service was installed:
Though repository, docker-compose prebuilt binary

Command used to create docker container (run/create/compose/screenshot)

rutorrent: image: linuxserver/rutorrent:v3.10-ls90 restart: unless-stopped environment: - PUID=1000 - PGID=1000 - TZ=Europe/Berlin ports: - 51413:51413 - 51413:51413/udp volumes: - ./certs:/certs - rutorrent_config:/config - rutorrent_downloads:/downloads