Jump to content

Docker

Luke

By Luke
in Linux

 Share

Recommended Posts

BAlGaInTl

BAlGaInTl   279

Posted
Posted
1 hour ago, lightsout said:

Anyone been able to upgrade to 4.8 on Docker/Unraid? The dashboard shows that there is an update, but I can get it to come up in docker. Using the official Emby image with this tag in the template "emby/embyserver:latest"

 

32 minutes ago, lightsout said:

I'm not exactly sure how to interpret that but it seems like it says it's out? Oh well I don't need to complicate things it will come when it does

I'm also running the official Emby docker image on Unraid.

I just did a refresh and mine is NOT indicating that there is an update yet. Current version from my dashboard is 4.7.14.0.

  • Like 1
Link to comment
Share on other sites
Edrock200

Edrock200   38

Posted
Posted (edited)
2 hours ago, BAlGaInTl said:

 

I'm also running the official Emby docker image on Unraid.

I just did a refresh and mine is NOT indicating that there is an update yet. Current version from my dashboard is 4.7.14.0.

As far as I can tell, the "latest" tag is still pointing to 4.7.14 for both linuxserver.io and emby repos. You'll have to manually update the tag to one of the 4.8 releases if you want to update. Note it's a one way upgrade, you cannot roll back. So backup your data folder first just in case. Would be nice if the emby copied the db's to something like *.db.4.7 prior to doing the one-way schema upgrades.

Edited by Edrock200
Link to comment
Share on other sites
BAlGaInTl

BAlGaInTl   279

Posted
Posted
2 hours ago, Edrock200 said:

As far as I can tell, the "latest" tag is still pointing to 4.7.14 for both linuxserver.io and emby repos. You'll have to manually update the tag to one of the 4.8 releases if you want to update. Note it's a one way upgrade, you cannot roll back. So backup your data folder first just in case. Would be nice if the emby copied the db's to something like *.db.4.7 prior to doing the one-way schema upgrades.

Is there a reason that it hasn't been updated to 4.8 as the latest for Docker? 

Is it just because it's a big change?

Link to comment
Share on other sites
hjason7812

hjason7812   25

Posted
Posted
On 10/13/2014 at 8:29 PM, Luke said:

I've kicked off a new docker build. keep in mind we have some new dependencies that have not been incorporated into docker yet, but we'll get it in for the next server release.

 

libwebp - 0.4.1

MediaInfo

Even the truenas core version is still the old one even when you try to force the update it won't due to the links are all still previous versions. 

Link to comment
Share on other sites
Luke Emby Team

Luke   37056

Posted
  • Author
Posted

Hi, it's coming. Apologies for the delay.

  • Like 2
  • Thanks 3
Link to comment
Share on other sites
Trapperjohn61

Trapperjohn61   9

Posted
Posted

Hi,

Fyi Linuxserver has the updated version but not the official Emby repository 

I use the official one

Thank you,

Bryan

@Luke

  • Agree 2
Link to comment
Share on other sites
Nabukodonosor

Nabukodonosor   11

Posted
Posted

Why does it take so long to update the official Emby repository?! Should I switch to Linuxserver?

  • Like 2
Link to comment
Share on other sites
Adamaen

Adamaen   2

Posted
Posted
4 hours ago, Nabukodonosor said:

Why does it take so long to update the official Emby repository?! Should I switch to Linuxserver?

Or after months of waiting, just wait one or two day more 🙂

  • Like 1
Link to comment
Share on other sites
Trapperjohn61

Trapperjohn61   9

Posted
Posted
18 minutes ago, Adamaen said:

Or after months of waiting, just wait one or two day more 🙂

Not sure of the process

but one would think that the official repository would be update 1st then others just asking 

 

Link to comment
Share on other sites
Nabukodonosor

Nabukodonosor   11

Posted
Posted

Yeah, I was thinking the same thing. Or just don't announce anything until you have it uploaded. :D

Link to comment
Share on other sites
StevenDTX

StevenDTX   2

Posted
Posted

I saw the post about 4.8 being released, so I removed the beta tag from my unRAID Docker.  Had a little oh crap moment when it didnt come back up.  Glad to find out the "latest" tag isnt updated to 4.8 yet.

Link to comment
Share on other sites
Luke Emby Team

Luke   37056

Posted
  • Author
Posted

Hi. The Docker release is coming. Apologies for the delay.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
Trapperjohn61

Trapperjohn61   9

Posted
Posted
5 minutes ago, Luke said:

Hi. The Docker release is coming. Apologies for the delay.

Thank you luke

sorry to bother you about this

  • Thanks 1
Link to comment
Share on other sites
jaycedk

jaycedk   378

Posted
Posted

Updated no issues to speak off.

Good job guys 👍

Now to investigate whats new 😂🤣 

Link to comment
Share on other sites
DeNiX

DeNiX   0

Posted
Posted

Hi there, 

I'm unable to create new api keys in latest beta version, running a docker container.  (fresh install) 
If I create a separate container with tag latest, this works as expected and api keys get created. 

Anybody else also experiencing this too? 

Link to comment
Share on other sites
jaycedk

jaycedk   378

Posted
Posted
7 minutes ago, DeNiX said:

Hi there, 

I'm unable to create new api keys in latest beta version, running a docker container.  (fresh install) 
If I create a separate container with tag latest, this works as expected and api keys get created. 

Anybody else also experiencing this too? 

Yes had that happen to me to.

But I ran beta to test, guess the beta period is over for now.

So will scrape that, and install a new when the new beta starts.

But not seeing this in 4.8.0.80 where i can create and delete.

Link to comment
Share on other sites
DeNiX

DeNiX   0

Posted
Posted

Thnx for the reply, i was using the beta since av1 support, never checked the latest versions to see if it was already available, but i just updated my main instance to latest, and happy to see that all is still working as expected, i was thinking if it aint broken dont fix it, since it was a pain in the ass to get it working in the first place :)

 

Link to comment
Share on other sites
Trapperjohn61

Trapperjohn61   9

Posted
Posted

Hi,

So I was able to upgrade Emby server. 
thank you

I also update the Emby apps on iPhone and ipad

i am also a premiere member and entered my key on Emby startup

when I go into backup and  restore I find that it does not see my current backups. 
so I uninstalled and reinstalled restore and backup and did the Emby restarts needed but it still does not see previous 4.7 backups. Always worked before

so I did a test and found if I do a backup it then sees the new backup but there are 2 files created backup full and databases 

I also wish to mention that when choosing the same backup folder I have used for years I find when I select it but do not hit ok I see my backups there so it does see the separate 4.7 backups with the ending auto.

 Am thinking there is a compatibility issue between 4.7 backups and 4.8?

just guessing 

 

Thank you for your help,

Bryan

Link to comment
Share on other sites
tattler

tattler   31

Posted
Posted
On 03/02/2024 at 13:26, Nabukodonosor said:

Why does it take so long to update the official Emby repository?! Should I switch to Linuxserver?

I am using the Linuxserver docker image. Just upgraded yesterday without a hitch! Kudos to Emby team! Which repository should I use? Linuxserver or official Emby?

Link to comment
Share on other sites
Jeansy

Jeansy   2

Posted
Posted (edited)

Hi,

I updated my emby docker image to version 4.8.0.80.

Now it wouldn't start anymore, leaving me the following error in the log: 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
s6-envuidgid: fatal: unknown user: root
s6-envuidgid: fatal: unknown user: root
s6-envuidgid: fatal: unknown user: root
s6-envuidgid: fatal: unknown user: root
s6-envuidgid: fatal: unknown user: root
s6-envuidgid: fatal: unknown user: root
s6-envuidgid: fatal: unknown user: root
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
exec: fatal: unable to exec sh: Exec format error
[services.d] done.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

My docker-compose.yml looks like this: 

name: emby

services:
  app:
    container_name: emby
    environment:
      - TZ=Europe/Berlin
      - UID=1000
      - GID=1000
      - GIDLIST=1000
    image: emby/embyserver:latest
    networks:
      - network
    restart: always
    ports:
      - 8096:8096
    volumes:
      - /mnt/m/emby/programdata:/config
      - /mnt/f:/mnt/f

networks:
  network:
    external: true

Does anyone else struggle with this problem or has a hint for me how to fix it?

Edited by Jeansy
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...