Docker

[Happy2Play 8252]

1 minute ago, cypher0117 said:

I wouldn't expect that to cause what I'm seeing, but I can definitely repeat it by going back to 4.6.4.0.  Any connections that are remote are not seen as remote.

But this has to be specific to your setup or everyone would be experiencing this.

I would open your own topic in this Linux section going over your setup and your issue as this topic is to generic.

[Luke 37022]

On 7/18/2021 at 9:29 PM, Happy2Play said:

But this has to be specific to your setup or everyone would be experiencing this.

I would open your own topic in this Linux section going over your setup and your issue as this topic is to generic.

Yes @cypher0117, yes please open a new topic. Thanks.

[cypher0117 4]

On 7/21/2021 at 1:01 PM, Luke said:

Yes @cypher0117, yes please open a new topic. Thanks.

Reporting back.  I did not open a separate topic since I was able to get rid of my issue.  I ended up pruning and forcing a complete rebuild of the latest Emby docker and this seemed to fix my issue.

[Luke 37022]

1 hour ago, cypher0117 said:

Reporting back.  I did not open a separate topic since I was able to get rid of my issue.  I ended up pruning and forcing a complete rebuild of the latest Emby docker and this seemed to fix my issue.

Thanks for the feedback.

[computermachine 0]

I have a container set to work with a reverse proxy, that had worked for one evening, and then the next day on simply started throwing 502 errors.

This is what I have in my docker-compose.yml, excluding other containers (that work, but aren't relevant):

version: '3.8'

services:
  proxy:
    build: ./Proxy
    container_name: proxy
    restart: unless-stopped
    ports:
      - 80:80
      - 443:443
    labels:
      com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
    volumes:
      - ./volumes/Proxy/certs:/etc/nginx/certs:ro
      - ./volumes/Proxy/vhost.d:/etc/nginx/vhost.d
      - ./volumes/Proxy/html:/usr/share/nginx/html
      - /var/run/docker.sock:/tmp/docker.sock:ro
    networks:
      - proxy-tier

  letsencrypt-companion:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt
    restart: unless-stopped
    volumes:
      - ./volumes/Proxy/certs:/etc/nginx/certs
      - ./volumes/Proxy/acme:/etc/acme.sh
      - ./volumes/Proxy/vhost.d:/etc/nginx/vhost.d
      - ./volumes/Proxy/html:/usr/share/nginx/html
      - /var/run/docker.sock:/var/run/docker.sock:ro
    networks:
      - proxy-tier
    depends_on:
      - proxy

  emby:
    image: emby/embyserver:latest
    container_name: emby
    restart: unless-stopped
    volumes:
      - ./volumes/Emby/config:/config
      - ../Media/Videos/Movies:/Movies:ro
      - ../Media/Videos/TV:/TV:ro
      - ../Media/YourClassical.org:/Music/Classical_Music:ro
    devices:
      - /dev/dri:/dev/dri
    ports:
      - 8096:8096
#    env_file:
#      - ./Emby/cert.env
#      - ./Emby/config.env
    environment:
      - VIRTUAL_HOST=sub.domain.tld
      - LETSENCRYPT_HOST=sub.domain.tld
      - LETSENCRYPT_EMAIL=redacted
      - VIRTUAL_PORT=443
      - APP_UID=2
      - APP_GID=2
      - TZ="New York"
      - GIDLIST=107,44,107
    networks:
      - proxy-tier

volumes:
  certs:
  acme:
  vhost.d:
  html:

networks:
  proxy-tier:

My issue is that when I connect locally via hostname:8096 (or internal IP:8096), it provides the container's internal IP for local (which I can correct by filling in the "Local IP Address" under Network, and the URL provided for WAN throws a 502 (with sub.domain.tld set on port 443 with reverse proxy set for security). Any attempt at switching the port to 8920 (port is currently forward on router) results in the browser immediately saying there's no connection.

The proxy above is jwilder/nginx-proxy:alpine.

Any ideas what's going on?

[ertagon2 44]

46 minutes ago, computermachine said:

I have a container set to work with a reverse proxy, that had worked for one evening, and then the next day on simply started throwing 502 errors.

This is what I have in my docker-compose.yml, excluding other containers (that work, but aren't relevant):

version: '3.8'

services:
  proxy:
    build: ./Proxy
    container_name: proxy
    restart: unless-stopped
    ports:
      - 80:80
      - 443:443
    labels:
      com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
    volumes:
      - ./volumes/Proxy/certs:/etc/nginx/certs:ro
      - ./volumes/Proxy/vhost.d:/etc/nginx/vhost.d
      - ./volumes/Proxy/html:/usr/share/nginx/html
      - /var/run/docker.sock:/tmp/docker.sock:ro
    networks:
      - proxy-tier

  letsencrypt-companion:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt
    restart: unless-stopped
    volumes:
      - ./volumes/Proxy/certs:/etc/nginx/certs
      - ./volumes/Proxy/acme:/etc/acme.sh
      - ./volumes/Proxy/vhost.d:/etc/nginx/vhost.d
      - ./volumes/Proxy/html:/usr/share/nginx/html
      - /var/run/docker.sock:/var/run/docker.sock:ro
    networks:
      - proxy-tier
    depends_on:
      - proxy

  emby:
    image: emby/embyserver:latest
    container_name: emby
    restart: unless-stopped
    volumes:
      - ./volumes/Emby/config:/config
      - ../Media/Videos/Movies:/Movies:ro
      - ../Media/Videos/TV:/TV:ro
      - ../Media/YourClassical.org:/Music/Classical_Music:ro
    devices:
      - /dev/dri:/dev/dri
    ports:
      - 8096:8096
#    env_file:
#      - ./Emby/cert.env
#      - ./Emby/config.env
    environment:
      - VIRTUAL_HOST=sub.domain.tld
      - LETSENCRYPT_HOST=sub.domain.tld
      - LETSENCRYPT_EMAIL=redacted
      - VIRTUAL_PORT=443
      - APP_UID=2
      - APP_GID=2
      - TZ="New York"
      - GIDLIST=107,44,107
    networks:
      - proxy-tier

volumes:
  certs:
  acme:
  vhost.d:
  html:

networks:
  proxy-tier:

My issue is that when I connect locally via hostname:8096 (or internal IP:8096), it provides the container's internal IP for local (which I can correct by filling in the "Local IP Address" under Network, and the URL provided for WAN throws a 502 (with sub.domain.tld set on port 443 with reverse proxy set for security). Any attempt at switching the port to 8920 (port is currently forward on router) results in the browser immediately saying there's no connection.

The proxy above is jwilder/nginx-proxy:alpine.

Any ideas what's going on?

This is really not enough information to say anything conclusively.

But here is what I have running on my remote box.
I have emby running on global localhost on port 8096 with the reverse proxy from domain to localhost:8096.

I don't like dealing with nginx in docker because I always end up running into bunch of issues with how the network is handled.
It seems like a configuration problem.

[aptalca 70]

1 hour ago, computermachine said:

I have a container set to work with a reverse proxy, that had worked for one evening, and then the next day on simply started throwing 502 errors.

This is what I have in my docker-compose.yml, excluding other containers (that work, but aren't relevant):

version: '3.8'

services:
  proxy:
    build: ./Proxy
    container_name: proxy
    restart: unless-stopped
    ports:
      - 80:80
      - 443:443
    labels:
      com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
    volumes:
      - ./volumes/Proxy/certs:/etc/nginx/certs:ro
      - ./volumes/Proxy/vhost.d:/etc/nginx/vhost.d
      - ./volumes/Proxy/html:/usr/share/nginx/html
      - /var/run/docker.sock:/tmp/docker.sock:ro
    networks:
      - proxy-tier

  letsencrypt-companion:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt
    restart: unless-stopped
    volumes:
      - ./volumes/Proxy/certs:/etc/nginx/certs
      - ./volumes/Proxy/acme:/etc/acme.sh
      - ./volumes/Proxy/vhost.d:/etc/nginx/vhost.d
      - ./volumes/Proxy/html:/usr/share/nginx/html
      - /var/run/docker.sock:/var/run/docker.sock:ro
    networks:
      - proxy-tier
    depends_on:
      - proxy

  emby:
    image: emby/embyserver:latest
    container_name: emby
    restart: unless-stopped
    volumes:
      - ./volumes/Emby/config:/config
      - ../Media/Videos/Movies:/Movies:ro
      - ../Media/Videos/TV:/TV:ro
      - ../Media/YourClassical.org:/Music/Classical_Music:ro
    devices:
      - /dev/dri:/dev/dri
    ports:
      - 8096:8096
#    env_file:
#      - ./Emby/cert.env
#      - ./Emby/config.env
    environment:
      - VIRTUAL_HOST=sub.domain.tld
      - LETSENCRYPT_HOST=sub.domain.tld
      - LETSENCRYPT_EMAIL=redacted
      - VIRTUAL_PORT=443
      - APP_UID=2
      - APP_GID=2
      - TZ="New York"
      - GIDLIST=107,44,107
    networks:
      - proxy-tier

volumes:
  certs:
  acme:
  vhost.d:
  html:

networks:
  proxy-tier:

My issue is that when I connect locally via hostname:8096 (or internal IP:8096), it provides the container's internal IP for local (which I can correct by filling in the "Local IP Address" under Network, and the URL provided for WAN throws a 502 (with sub.domain.tld set on port 443 with reverse proxy set for security). Any attempt at switching the port to 8920 (port is currently forward on router) results in the browser immediately saying there's no connection.

The proxy above is jwilder/nginx-proxy:alpine.

Any ideas what's going on?

502 means nginx can't reach the upstream service. Check the address you used for the emby container and make sure it's reachable or resolvable by nginx. Here's info for SWAG (which is also nginx based) and 502: https://docs.linuxserver.io/general/swag#502

not all of it applies but you get the idea

[pr0nstache 0]

I'm having trouble getting my config directory to work in docker-compose.  Here's my file, which works with the config line commented out.

---
version: "2.3"
services:
  emby:
    image: emby/embyserver
    container_name: embyserver
#    runtime: nvidia # Expose NVIDIA GPUs
#    network_mode: host # Enable DLNA and Wake-on-Lan
    environment:
      - UID=1000 # The UID to run emby as (default: 2)
      - GID=1000 # The GID to run emby as (default 2)
      - GIDLIST=1000 # A comma-separated list of additional GIDs to run emby as (default: 2)
    volumes:
#      - /mnt/storage/apps/emby/configure:/config # Configuration directory
      - /mnt/storage:/mnt/storage # Media directory
#      - /path/to/movies:/mnt/share2 # Media directory
    ports:
      - 8096:8096 # HTTP port
      - 8920:8920 # HTTPS port
    devices:
      - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes
#      - /dev/vchiq:/dev/vchiq # MMAL/OMX on Raspberry Pi
    restart: unless-stopped

If I uncomment the config line, the container exits with the attached errors.  I've checked permissions, and even ran a sudo chmod -R 777 on /mnt/storage/apps/emby/configure just to see if it was having permissions issues.  Emby did create directories in the location, and the log attached came from the configure/logs directory, so it does have access.

Thank you for the advice and suggestions you may have.

 

This is a mergerfs volume with 2 current disks in the pool.

embyserver-63767411332.txt

[Q-Droid 634]

Is the path /mnt/storage/apps/emby/configure a network share?

If it is then don't.

 

[Luke 37022]

5 hours ago, pr0nstache said:

I'm having trouble getting my config directory to work in docker-compose.  Here's my file, which works with the config line commented out.

---
version: "2.3"
services:
  emby:
    image: emby/embyserver
    container_name: embyserver
#    runtime: nvidia # Expose NVIDIA GPUs
#    network_mode: host # Enable DLNA and Wake-on-Lan
    environment:
      - UID=1000 # The UID to run emby as (default: 2)
      - GID=1000 # The GID to run emby as (default 2)
      - GIDLIST=1000 # A comma-separated list of additional GIDs to run emby as (default: 2)
    volumes:
#      - /mnt/storage/apps/emby/configure:/config # Configuration directory
      - /mnt/storage:/mnt/storage # Media directory
#      - /path/to/movies:/mnt/share2 # Media directory
    ports:
      - 8096:8096 # HTTP port
      - 8920:8920 # HTTPS port
    devices:
      - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes
#      - /dev/vchiq:/dev/vchiq # MMAL/OMX on Raspberry Pi
    restart: unless-stopped

If I uncomment the config line, the container exits with the attached errors.  I've checked permissions, and even ran a sudo chmod -R 777 on /mnt/storage/apps/emby/configure just to see if it was having permissions issues.  Emby did create directories in the location, and the log attached came from the configure/logs directory, so it does have access.

Thank you for the advice and suggestions you may have.

 

This is a mergerfs volume with 2 current disks in the pool.

embyserver-63767411332.txt 38.09 kB · 3 downloads

I don't have the solution for you as it is specific to your environment and container but it looks the server is unable to read or write from the path you're setting.

[pr0nstache 0]

1 hour ago, Luke said:

I don't have the solution for you as it is specific to your environment and container but it looks the server is unable to read or write from the path you're setting.

Thanks, I'm reaching out to mergerfs about this too.  I can write directly to one of the disks in the pool, but not to the mergerfs volume, and about half the containers I set up seem to be having this problem now, and half are working fine.

  

1 hour ago, Q-Droid said:

Is the path /mnt/storage/apps/emby/configure a network share?

If it is then don't.

 

It is a mergerfs volume with 2 disks currently added.  Read and write seems fine for everything except config directories from (some) docker containers.  I'll post a fix from mergerfs if there is one for anyone else using mergerfs/snapraid for their storage with a docker-compose for emby.  The read/write error for config directories seems to effect Emby, Sonarr, Radarr... but not Lidarr, Calibre, qbittorrent, tvheadend... weird.

Edited September 17, 2021 by pr0nstache
added reply

[Q-Droid 634]

I think the common element there is sqlite, possibly with mmap enabled that's causing problems with mergerfs.

You can also expect DB performance to be less than ideal in that configuration.

 

 

Edited September 17, 2021 by Q-Droid

[Trevor68 48]

Hi all, after noticing that Docker Desktop now works with Windows 10 and sucessfully setting up a pi-hole container, I decided to have a crack at Emby on W10 as a Docker Container too. 

I managed to get it up and running using the following command. 

docker run -d --name emby-server --restart unless-stopped -p 8096:8096/tcp emby/embyserver:latest

Now I am struggling with storage, as when I go to create a library I'm pretty sure I can only see folders inside Docker Desktop, as in I cannot navigate outside to my C drive. 

I presume i need to setup some sort of share volume for Docker? I did try using the docker gui, but it seems to want me to purchase pro to get the full ability to set anything but the volume name. 

I also just realised maybe this does belong in the linux forum, as by default Docker Desktop is running linux containers, not windows ones. 

[mastrmind11 717]

On 9/23/2021 at 2:07 AM, Trevor68 said:

Hi all, after noticing that Docker Desktop now works with Windows 10 and sucessfully setting up a pi-hole container, I decided to have a crack at Emby on W10 as a Docker Container too. 

I managed to get it up and running using the following command. 

docker run -d --name emby-server --restart unless-stopped -p 8096:8096/tcp emby/embyserver:latest

Now I am struggling with storage, as when I go to create a library I'm pretty sure I can only see folders inside Docker Desktop, as in I cannot navigate outside to my C drive. 

I presume i need to setup some sort of share volume for Docker? I did try using the docker gui, but it seems to want me to purchase pro to get the full ability to set anything but the volume name. 

I also just realised maybe this does belong in the linux forum, as by default Docker Desktop is running linux containers, not windows ones. 

not really sure how windows docker works but it seems to me you need to map your volumes.  hve a look here https://hub.docker.com/r/emby/embyserver

[Luke 37022]

We have not done any docker testing on windows just fyi.

[NikeSwe 65]

Don't know if this is beta related but I just updated and now the container dies with

libgcc_s.so.1 must be installed for pthread_cancel to work
Aborted

[alucryd 214]

@NikeSweIt's only the beta, I'm on it.

Edit: x64 is fixed, armv7 and armv8 will follow suite, sorry about the breakage.

Edited October 29, 2021 by alucryd

[lawrencecurtis 5]

Docker has not yet updated to 4.6.5.0

[Luke 37022]

4 hours ago, lawrencecurtis said:

Docker has not yet updated to 4.6.5.0

Hi, it should be up soon. Thanks.

[lawrencecurtis 5]

7 hours ago, Luke said:

Hi, it should be up soon. Thanks.

Sadly this still hasn’t updated

[alucryd 214]

Docker stable is up guys, thank you for your patience, please let us know if you run into any issue.

[KoRnEr007 2]

No issue about SSL like linux?

[alucryd 214]

2 minutes ago, KoRnEr007 said:

No issue about SSL like linux?

Not in my testing. Linux is being fixed as we speak, if your main installation is on Linux you might want to wait a bit for a fix instead of switching to docker, it will be available later today.

[KoRnEr007 2]

No, but my server is on docker Debian

[KoRnEr007 2]

A 4.6.6 will be out, i am waiting before update even on docker