Docker

[Luke 42077]

Android has it's own code base.

[Guest Normal]

Oh, so the changes I made to the language file and mediainfo file need to be ported to it (if they are accepted).

Except the android code base is open source too. Didn't find it on github.

Edited September 25, 2018 by Normal

[Friday13th 0]

Hey There!

i have a question abount the external emby connect access .

i am using embywith a reverse proxy

here is my compose file

version: '3.7'
services:
  emby:
    container_name: emby
    restart: always
    image: emby/embyserver
    volumes:
      - /sharedfolders/AppData/emby:/config
      - /sharedfolders/Homeserver/Media:/mnt/share1
      - /sharedfolders/AppData/shared:/shared
    ports:
      - "8096:8096/tcp"
      - "8920:8920/tcp"
#      - "8097:8097/tcp"
    environment:
#      - TZ=Europe/Berlin
      - UID=1000
      - GID=1000
      - GIDLIST=100
    networks:
      - web
    labels:
      - "traefik.enable=true"
      - "traefik.backend=emby"
      - "traefik.frontend.rule=Host:emby.mydomain.de"
#      - "traefik.port=8920"
#      - "traefik.protocol=https"
      - "traefik.port=8096"
      - "traefik.protocol=http"
      - "traefik.docker.network=web"
      - "traefik.frontend.headers.SSLRedirect=true"
#      - "traefik.frontend.auth.digest.usersFile=/shared/.htdigest"
#      - "traefik.frontend.auth.digest.removeHeader=true"
      - "traefik.frontend.headers.STSSeconds=315360000"
      - "traefik.frontend.headers.browserXSSFilter=true"
      - "traefik.frontend.headers.contentTypeNosniff=true"
      - "traefik.frontend.headers.forceSTSHeader=true"
      - "traefik.frontend.headers.STSIncludeSubdomains=true"
      - "traefik.frontend.headers.STSPreload=true"
      - "traefik.frontend.headers.frameDeny=true"

networks:
  web:
    external: true

So i can use emby in my homenetwork on the servers ip on port 8096 without any issue.

i can also use emby on my domain emby.mydomain.de.

if i am mapping port 8096 on my router to port 8096 to my servers ip emby connect is working fine.

 

normally i am using htdigest authentification on my reverse proxy.

 

my goal is to use emby connect without opening the port on my router using the emby.mydomain.de domain and without the issue that everyone can access my emby server

 

i can do that if i turn of the auth but then i can just open emby on the domain without loging in - so its open for everyone 

 

i tried to put the remote access to another port and using the proxy on this port (so for example external port 8097, reverse proxy emby.mydomain.de --> 192.168.xxx.xxx:8097) but it was not working

i tried setting the external address  to emby.mydomain.de and 192.168.xxx.1 (router ip) but both didnt worked.

 

 

What am i doing wrong and how can i do it with the reverse proxy?

[Luke 42077]

I would suggest opening a new topic because other reverse proxy users will see that and will probably jump in and offer their advice. Thanks !

[vaise 340]

Emby on docker, Letsencrypt listens on port 443, want to use QOS but cant figure out the port to set in the QOS rules?

letsencrypt listens on 443, reverse proxies to emby on 8096.

I want to set some QOS rules on the port, but I cant even see any sessions on the router when someone is remotely watching my emby system ?

Any pointers ?

 

Thanks.

[Luke 42077]

I would try one, then the other, and compare your results. Please let us know how you get on. Thanks !

[NikeSwe 122]

Just switched to Unraid and running the official Docker, beta version. I don't know where to post this. New thread in the testing part?

 

Emby dies when scanning library. Adding new stuff and the container crash all the time.

 

Getting unhandled_980e5e1c-eb5b-4111-9f27-9394bb66bb89.txt-logs with:

 

 

System.InvalidOperationException: No process is associated with this object.
Source: System.Diagnostics.Process
TargetSite: Void EnsureState(State)
   at System.Diagnostics.Process.EnsureState(State state)
   at System.Diagnostics.Process.EnsureState(State state)
   at System.Diagnostics.Process.GetStat()
   at System.Diagnostics.Process.get_StartTimeCore()
   at System.Diagnostics.Process.get_StartTime()
   at Emby.Server.MediaEncoding.ProcessRun.Extensions.ProcessCpuMonitor.TimerCallback(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers()

 

 

Last in log:
 

 

 

2018-10-06 10:34:23.780 Debug MediaEncoder: Ffmpeg -f matroska -ss 00:40:00.000 -i file:"abc.mkv" -threads 0 -v quiet -vframes 1 -vf "scale=600:trunc(ow/a/2)*2,thumbnail=24" -f image2 "/config/cache/temp/d159c0f6-eb30-401f-8da8-04711fb13149.jpg"
2018-10-06 10:34:23.780 Info MediaEncoder: ProcessRun 'ffmpgeg extract-image' Execute: /bin/ffmpeg -f matroska -ss 00:40:00.000 -i file:"abc.mkv" -threads 0 -v quiet -vframes 1 -vf "scale=600:trunc(ow/a/2)*2,thumbnail=24" -f image2 "/config/cache/temp/d159c0f6-eb30-401f-8da8-04711fb13149.jpg"
2018-10-06 10:34:23.868 Info MediaEncoder: ProcessRun 'ffmpgeg extract-image' Started.
2018-10-06 10:34:24.125 Error Main: UnhandledException
*** Error Report ***
Version: 3.6.0.52
Command line: /system/EmbyServer.dll -programdata /config -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
Operating system: Unix 4.18.10.0
64-Bit OS: True
64-Bit Process: True
User Interactive: True
Processor count: 4
Program data path: /config
Application directory: /system
System.InvalidOperationException: No process is associated with this object.
Source: System.Diagnostics.Process
TargetSite: Void EnsureState(State)
    at System.Diagnostics.Process.EnsureState(State state)
    at System.Diagnostics.Process.EnsureState(State state)
    at System.Diagnostics.Process.GetStat()
    at System.Diagnostics.Process.get_StartTimeCore()
    at System.Diagnostics.Process.get_StartTime()
    at Emby.Server.MediaEncoding.ProcessRun.Extensions.ProcessCpuMonitor.TimerCallback(Object state)
    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
    at System.Threading.TimerQueueTimer.CallCallback()
    at System.Threading.TimerQueueTimer.Fire()
    at System.Threading.TimerQueue.FireNextTimers()

 

 

Guess you want full log, can provide later. Just wanted to see if someone has a clue? Thinks it happens while extracting thumbs?

Edited October 6, 2018 by NikeSwe

[mastrmind11 722]

Just switched to Unraid and running the official Docker, beta version. I don't know where to post this. New thread in the testing part?

 

Emby dies when scanning library. Adding new stuff and the container crash all the time.

 

Getting unhandled_980e5e1c-eb5b-4111-9f27-9394bb66bb89.txt-logs with:

 

 

 

Last in log:

 

 

 

Guess you want full log, can provide later. Just wanted to see if someone has a clue? Thinks it happens while extracting thumbs?

2018-10-06 10:34:23.868 Info MediaEncoder: ProcessRun 'ffmpgeg extract-image' Started.
2018-10-06 10:34:24.125 Error Main: UnhandledException

disable image extraction and see what happens.

[NikeSwe 122]

2018-10-06 10:34:23.868 Info MediaEncoder: ProcessRun 'ffmpgeg extract-image' Started.
2018-10-06 10:34:24.125 Error Main: UnhandledException

disable image extraction and see what happens.

 

That's what I did to make it scan my new library and it did it successfully.

Executed the scheduled task for chapter image extraction and it worked out good too. But, not so much new material in thar library yet..

Edited October 6, 2018 by NikeSwe

[softworkz 5066]

Just switched to Unraid and running the official Docker, beta version. I don't know where to post this. New thread in the testing part?

 

Emby dies when scanning library. Adding new stuff and the container crash all the time.

 

Getting unhandled_980e5e1c-eb5b-4111-9f27-9394bb66bb89.txt-logs with:

 

 

 

Last in log:

 

 

 

Guess you want full log, can provide later. Just wanted to see if someone has a clue? Thinks it happens while extracting thumbs?

 

Yes, could you please post or PM the full logs.

 

Thank you!

[Luke 42077]

It's resolved for the next beta update. Going forward please use the Testing Area of the community for beta discussion. Thanks.

[NikeSwe 122]

It's resolved for the next beta update. Going forward please use the Testing Area of the community for beta discussion. Thanks.

Great! Thanks! 

Posted here because new to Unraid and Docker. Did not know if it was general Docker-problem or Emby-problem. Will remember to post in the testing area in the future when running the beta.

[Luke 42077]

Thanks !

[tuumke 0]

As of a few days, my servers keeps crashing when using an SMB library.

I'm using 2 RasPi3 with OSMC and i wanted to start using the emby addon. I thought i needed SMB libraries in EMBY as well then so i changed them, but it just keeps crashing now.

 

Running un unRAID nas with emby in a docker container.

 

put my logs up here: https://pastebin.com/sc3J9HmP

i cant find anything that points to why its crashing.. docker just stops.

These are my docker logs: https://pastebin.com/3Td3Xrhe

 

Docker logs show a segmantation fault, i already turned off the realtime scan.

 

-edit-

 

I switched my libraries back to local folder with the "(Optional) Shared network folder" network location set.

Will check my (clean) osmc install later this week. Emby doesnt seem to crash anymore

Edited October 10, 2018 by tuumke

[Luke 42077]

As of a few days, my servers keeps crashing when using an SMB library.

I'm using 2 RasPi3 with OSMC and i wanted to start using the emby addon. I thought i needed SMB libraries in EMBY as well then so i changed them, but it just keeps crashing now.

 

Running un unRAID nas with emby in a docker container.

 

put my logs up here: https://pastebin.com/sc3J9HmP

i cant find anything that points to why its crashing.. docker just stops.

These are my docker logs: https://pastebin.com/3Td3Xrhe

 

Docker logs show a segmantation fault, i already turned off the realtime scan.

 

-edit-

 

I switched my libraries back to local folder with the "(Optional) Shared network folder" network location set.

Will check my (clean) osmc install later this week. Emby doesnt seem to crash anymore

 

Yea, I think it is SMB related. We're looking into it, thanks.

[jstnchristian 0]

Hi there,

 

I'm trying to get Emby installed on my RPi 3 and docker. I don't seem to be getting the right fs image, though:

# pi @ pitv in ~/media/tv [2:16:15] 
$ docker run -d \              
--volume /home/pi/configs/emby:/config \
--volume /home/pi/media:/mnt/share1 \
--publish 8096:8096 \
--env UID=1000 \
--env GID=100 \
--env GIDLIST=100 \
emby/embyserver:latest
475d877141c0c1a30119ec88c2701d27f0e727e964aa38db3f2e646e22f7a2d3

# pi @ pitv in ~/media/tv [2:16:27] 
$ docker logs 475d877141c0c1a30119ec88c2701d27f0e727e964aa38db3f2e646e22f7a2d3
standard_init_linux.go:190: exec user process caused "exec format error"

Wanted to make sure armv7 is actually supported for docker installs. I saw that a few arches were taken out during a recent upgrade.

 

Thanks!

 

-edit-

 

Tried the beta tag, same result

Edited October 23, 2018 by jstnchristian

[Luke 42077]

Have you tried the armhf version?

[jstnchristian 0]

Apologies, my docker-fu is pretty rudimentary. Is there a switch to force a certain version? Using emby/embyserver:armv7 and emby/embyserver:armhf give me

docker: Error response from daemon: manifest for emby/embyserver:armhf not found.

[Luke 42077]

Can you supply the full output? thanks.

[jstnchristian 0]

Sure:

# pi @ pitv in ~ [21:17:41] C:130
$ uname -a                                                                    
Linux pitv 4.14.50-v7+ #1122 SMP Tue Jun 19 12:26:26 BST 2018 armv7l GNU/Linux

# pi @ pitv in ~ [21:17:46] 
$ for i in beta latest; do echo emby/embyserver:$i; docker inspect emby/embyserver:$i | grep Arch; done

emby/embyserver:beta
        "Architecture": "amd64",
emby/embyserver:latest
        "Architecture": "amd64",

# pi @ pitv in ~ [21:17:50] 
$ for i in armhf armv7; do docker pull emby/embyserver:$i; done               
Error response from daemon: manifest for emby/embyserver:armhf not found
Error response from daemon: manifest for emby/embyserver:armv7 not found

For some reason, it looks like the amd64 image is being pulled, as opposed to the armv7

[jstnchristian 0]

Actually, looks like the embyserver manifest doesn't include the arm platform:

$ docker manifest inspect emby/embyserver -v                                                           
{                                                                                                      
        "Ref": "docker.io/emby/embyserver:latest",                                                     
        "Descriptor": {                                                                                
                "mediaType": "application/vnd.docker.distribution.manifest.v2+json",                   
                "digest": "sha256:6aa2dbfb6b9a109aeae58b72c8453bd194bfe346f5244453d046d79a9c35c2b8",  
                "size": 1371,
                "platform": {
                        "architecture": "amd64",
                        "os": "linux"
                }
        },
        "SchemaV2Manifest": { "Lots of stuff in here that isn't relevant" }
}

Perhaps I should raise an issue in the Git repo?

[Luke 42077]

That's because it's a separate docker container. We have three different containers depending on architecture:

 

https://hub.docker.com/u/emby/

 

We'll update our download page instructions. Thanks.

[jstnchristian 0]

Got it, thanks!

 

-edit-

 

Runs like a dream!

Edited October 25, 2018 by jstnchristian

[Luke 42077]

Thanks for the feedback !

[vaise 340]

Hi docker people.  I am using the embybeta docker on unraid.

I find I need to make some database deletes manually due to an issue with the database after moving some shares around.

I have simulated the edits I need to do on a copy of the library.db - copied to my local PC, using DB Browser for SQLLite installed on my PC.

I am wondering if the below instructions will be valid for the docker to do this :

 

1 - stop emby server

2 - map a drive to the appdata share (where the dockers live)

3 - use DB Briwser fro SQLLite, open the library.db from the share

4 - Make the SQL edits

5 - Write Changes

6 - Close DB Browser for SQLLite 

7 - re-start emby server

 

Should I compact the database also ?

 

Thanks.

Edited October 29, 2018 by vaise