Docker

[darkassassin07 617]

The one off is great; but I'm looking for a change in your release procedure to include updating docker promptly with each comming update.

 

OR

 

Have docker based emby servers check docker hub for new releases before sending 'update available' notifications.

 

 

 

Please stop notifying docker users that an update is available when you have not actually made one available to them.

[Oracle 84]

On 4/22/2024 at 8:24 PM, darkassassin07 said:

Please stop notifying docker users that an update is available when you have not actually made one available to them.

Seconding this. 

 

@Luke - What is the normal release schedule for Docker container? Can we look into why these are not released at the same time as other release types?

 

Thanks.

[Luke 40003]

On 5/31/2024 at 10:56 AM, Oracle said:

Seconding this. 

 

@Luke - What is the normal release schedule for Docker container? Can we look into why these are not released at the same time as other release types?

 

Thanks.

HI, apologies, missed this posting. It is the same schedule as other platforms. It's just one of the last to build. In this case it was available the following morning. We'll try and shorten that gap of time. Thanks.

[Oracle 84]

22 hours ago, Luke said:

HI, apologies, missed this posting. It is the same schedule as other platforms. It's just one of the last to build. In this case it was available the following morning. We'll try and shorten that gap of time. Thanks.

Thanks, buddy! Appreciate what you and the team do.

[Capitano 4]

Can't seem to find this version?

[zer0ish 12]

3 hours ago, Capitano said:

Can't seem to find this version?

Mine has been on 4.8.8.0 for a good while now. Are you using the "latest" tag in your docker? I dont even use the latest tag and I get the latest version when it's pushed to docker.
This is the repo I use: emby/embyserver
No tag at the end but you can try:
emby/embyserver:latest

 

[zer0ish 12]

On another note, where did the option to add Specials from TV shows where they should be in the seasons they aired? And played when and where they should be in the seasons?

Used to be in Library > Advanced and a few other places over the years but now I can't find it anywhere. 
I only now noticed because I binged watched Futurama and the 3 specials I had didn't play this time around: The Beast with a billion backs, Bender's Game, Into the wild green yonder.

Was this removed or moved to somewhere I can't find?

I've been digging everywhere in the server settings and can't find it. Even in the Library for the TV shows it's no longer there either.

Thanks.

[Happy2Play 9431]

2 hours ago, zer0ish said:

On another note, where did the option to add Specials from TV shows where they should be in the seasons they aired? And played when and where they should be in the seasons?

Used to be in Library > Advanced and a few other places over the years but now I can't find it anywhere. 
I only now noticed because I binged watched Futurama and the 3 specials I had didn't play this time around: The Beast with a billion backs, Bender's Game, Into the wild green yonder.

Was this removed or moved to somewhere I can't find?

I've been digging everywhere in the server settings and can't find it. Even in the Library for the TV shows it's no longer there either.

Thanks.

Yes it has been removed and currently only Critical Story gets position data.

 

[Luke 40003]

On 6/25/2024 at 5:47 PM, zer0ish said:

On another note, where did the option to add Specials from TV shows where they should be in the seasons they aired? And played when and where they should be in the seasons?

Used to be in Library > Advanced and a few other places over the years but now I can't find it anywhere. 
I only now noticed because I binged watched Futurama and the 3 specials I had didn't play this time around: The Beast with a billion backs, Bender's Game, Into the wild green yonder.

Was this removed or moved to somewhere I can't find?

I've been digging everywhere in the server settings and can't find it. Even in the Library for the TV shows it's no longer there either.

Thanks.

HI, yes but more options to control this are likely for future updates. Thanks.

[darkassassin07 617]

On 4/22/2024 at 5:24 PM, darkassassin07 said:

The one off is great; but I'm looking for a change in your release procedure to include updating docker promptly with each comming update.

 

OR

 

Have docker based emby servers check docker hub for new releases before sending 'update available' notifications.

 

 

 

Please stop notifying docker users that an update is available when you have not actually made one available to them.

@Luke

 

 

[Luke 40003]

4 hours ago, darkassassin07 said:

@Luke

 

 

HI, it should be up in a day or so. Apologies for the delay.

[NEOMorphey 1]

Hi. 
Looks like on latest docker image AMD hardware encoding broken. docker image 4.8.9.0

/ # /bin/vainfo
Trying display: drm
libva info: VA-API version 1.18.0
libva info: Trying to open /lib/dri/radeonsi_drv_video.so
libva error: dlopen of /lib/dri/radeonsi_drv_video.so failed: /lib/dri/radeonsi_drv_video.so: undefined symbol: amdgpu_va_get_start_addr
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
/ # LDPRELOAD=/lib/dri/radeonsi_drv_video.so clinfo
Number of platforms                               0

ICD loader properties
  ICD loader Name                                 Khronos OpenCL ICD Loader
  ICD loader Vendor                               Khronos Group
  ICD loader Version                              3.0.5
  ICD loader Profile                              OpenCL 3.0

And it works on 4.8.8.0

[alucryd 238]

That's really odd, mesa drivers haven't been updated since May 7. Will look into it.

[alucryd 238]

@NEOMorpheyThe May 7 drivers actually didn't make it into 4.8.8.0, and I can reproduce. We will put a fixed release out shortly. Apologies for the disruption.

[alucryd 238]

@NEOMorpheyJust pushed 4.8.10.0, should restore VAAPI on AMD.

[NEOMorphey 1]

@alucrydYes. It is working now. Thank you very much for fast responses and quick fix.

[train_wreck 0]

I'm not sure whether to post this here or as a new post. I just installed the Docker version of Emby on a Raspberry Pi 4. I can't get it to save any of the config when the Pi reboots. Every time it reboots Emby acts like I just installed it, makes me create a new user, choose libraries. Doesn't appear to save anything at all. Any idea what to do here?

[Webdoc 2]

30 minutes ago, train_wreck said:

I'm not sure whether to post this here or as a new post. I just installed the Docker version of Emby on a Raspberry Pi 4. I can't get it to save any of the config when the Pi reboots. Every time it reboots Emby acts like I just installed it, makes me create a new user, choose libraries. Doesn't appear to save anything at all. Any idea what to do here?

At a guess you have not referenced a data folder in your docker volume code line

[raptorjr 14]

Hi

I guess all questions about Docker and Emby should go here, if I'm wrong just tell me and I will create a new thread.

Anyway, I had a working version of 4.7.14.0 on a standalone computer. And now I have bought a new computer where I will use Unraid and have Emby in a docker container instead. My problem is to restore the backup from the old computer. The new server can't see the old backups so I can't restore. I have set the path to the same shared drive where the backups are. And I have created the user/groups with relevant uid/gid(starting the Docker instance with these), and also everyone should be able to read the backup folder. But still, doesn't show up on the Backup & Restore page of the new server. What am I missing? Is it because of different versions? Can I in that case get the old version in the Docker first to make the restore and then update to latest?

Edited October 29, 2024 by raptorjr

[Q-Droid 878]

2 hours ago, raptorjr said:

Hi

I guess all questions about Docker and Emby should go here, if I'm wrong just tell me and I will create a new thread.

Anyway, I had a working version of 4.7.14.0 on a standalone computer. And now I have bought a new computer where I will use Unraid and have Emby in a docker container instead. My problem is to restore the backup from the old computer. The new server can't see the old backups so I can't restore. I have set the path to the same shared drive where the backups are. And I have created the user/groups with relevant uid/gid(starting the Docker instance with these), and also everyone should be able to read the backup folder. But still, doesn't show up on the Backup & Restore page of the new server. What am I missing? Is it because of different versions? Can I in that case get the old version in the Docker first to make the restore and then update to latest?

1. What OS is your current Emby server?

2. Is it already on Docker?

3. Can you upgrade before the migration?

I think the 4.8.x backup/restore tools are not backwards compatible with 4.7.x unless something has changed since.

 

[guunter 40]

10 hours ago, raptorjr said:

Hi

I guess all questions about Docker and Emby should go here, if I'm wrong just tell me and I will create a new thread.

Anyway, I had a working version of 4.7.14.0 on a standalone computer. And now I have bought a new computer where I will use Unraid and have Emby in a docker container instead. My problem is to restore the backup from the old computer. The new server can't see the old backups so I can't restore. I have set the path to the same shared drive where the backups are. And I have created the user/groups with relevant uid/gid(starting the Docker instance with these), and also everyone should be able to read the backup folder. But still, doesn't show up on the Backup & Restore page of the new server. What am I missing? Is it because of different versions? Can I in that case get the old version in the Docker first to make the restore and then update to latest?

You should be able to just pull the whole /var/lib/Emby folder and put it in the Emby appdata folder and then it should launch. I did the reverse and converted my docker to a proxmox lxc the same way. 

[raptorjr 14]

12 hours ago, Q-Droid said:

1. What OS is your current Emby server?

2. Is it already on Docker?

3. Can you upgrade before the migration?

I think the 4.8.x backup/restore tools are not backwards compatible with 4.7.x unless something has changed since.

 

The old is not Docker, and it is a Ubuntu 16.04. And it was because I got in trouble trying to upgrade I decided to go with a new computer and a more modern approach. But I still would like to restore the old Emby and not start all over. 
 

[raptorjr 14]

5 hours ago, guunter said:

You should be able to just pull the whole /var/lib/Emby folder and put it in the Emby appdata folder and then it should launch. I did the reverse and converted my docker to a proxmox lxc the same way. 

Thanks. I will try this. Can’t get any worse. 
 

Is there older Dockers available with 4.7? So I can start with that and restore and then update Enby. I’m not that experienced with Docker. 

[Q-Droid 878]

1 hour ago, raptorjr said:

Thanks. I will try this. Can’t get any worse. 
Is there older Dockers available with 4.7? So I can start with that and restore and then update Emby. I’m not that experienced with Docker. 

Since your migration is Linux-to-Linux you should be able to do what @guunter suggests. However, going to Unraid means you might want to ask in the pinned Unraid thread because it does things a bit differently.

You should be able to pull an older Emby Docker image and upgrade on the the destination.

In the end, if done right the backup/restore is not needed but you'll have to map the volumes in Docker to make the library paths look like the source system. Or if your libary is not big you can define new library paths and let it rescan.

Whatever you do - keep the source data until you have the new server running the way you want it.

 

 

 

Edited October 30, 2024 by Q-Droid

[guunter 40]

3 hours ago, raptorjr said:

Thanks. I will try this. Can’t get any worse. 
 

Is there older Dockers available with 4.7? So I can start with that and restore and then update Enby. I’m not that experienced with Docker. 

So when you edit the config you have to tell it to use a specific version. So where it says repository at the end of it you put :4.7.14 and it will lock it to that version. You can then do incremental upgrades that way to safely upgrade to the latest version.