Jump to content


Photo

[Docker] New Testing Image

docker tumbleweed suse

  • Please log in to reply
25 replies to this topic

#21 hurricanehrndz OFFLINE  

hurricanehrndz

    Advanced Member

  • Developers
  • 1249 posts
  • Local time: 02:44 AM

Posted 22 January 2016 - 08:30 PM

That is the latest stable

Sent from my D6603 using Tapatalk

#22 chuga OFFLINE  

chuga

    Advanced Member

  • Members
  • 136 posts
  • Local time: 05:44 AM

Posted 23 January 2016 - 10:31 AM

I get a page not found for this link?

https://github.com/M...-templates/Emby

where do I go for the new template?

 

thanks



#23 hurricanehrndz OFFLINE  

hurricanehrndz

    Advanced Member

  • Developers
  • 1249 posts
  • Local time: 02:44 AM

Posted 23 January 2016 - 10:32 AM

Sorry, it's here https://github.com/M...-templates/emby

Sent from my D6603 using Tapatalk

#24 hurricanehrndz OFFLINE  

hurricanehrndz

    Advanced Member

  • Developers
  • 1249 posts
  • Local time: 02:44 AM

Posted 23 January 2016 - 10:33 AM

Please visit the wiki for the most up to date information

Sent from my D6603 using Tapatalk

#25 chuga OFFLINE  

chuga

    Advanced Member

  • Members
  • 136 posts
  • Local time: 05:44 AM

Posted 23 January 2016 - 02:11 PM

Hi,

 

Not sure if I am doing this correctly.  The steps I did were:

1)  went to my dockers and chose "stop" for the current emby docker.

2)  clicked on docker repositories and pasted in "https://github.com/M...templates/emby"

3) went back to docker tab and clicked "add container", then "select a template" - "emby" -  "embyserver"

4) it autopopulated in the settings I had from the previous emby server docker (/mnt/cache/appdata/emby for /config, and /mnt for /mnt)

5) clicked save and let it go.

6) started the docker and went to the webgui - and it wants to start from scratch (welcome to Emby, create users, etc)

 

do I really have to recreate all of my users and custom settings etc?   I thought with the same volume mappings it would find my old configs?

 

also, why do both the old and new templates point toward

Container Page: https://registry.hub...mby/embyserver/

this seems to mean they are the same thing ?

 

thanks for the help,

 

(btw, I have not deleted my old emby docker yet....just have it "stopped")

 

I think it is working now - missed something simple.  The new docker defaults for volume mapping was just *almost* the same.  Except it used lowercase emby and I previously had Emby for the appdata/Emby directory.  Fixed the case and it detected my settings.  Sorry for the bother - maybe this helps someone else with this issue in the future.


Edited by chuga, 23 January 2016 - 05:06 PM.

  • hurricanehrndz likes this

#26 hurricanehrndz OFFLINE  

hurricanehrndz

    Advanced Member

  • Developers
  • 1249 posts
  • Local time: 02:44 AM

Posted 24 January 2016 - 12:26 AM

Hi,

 

Not sure if I am doing this correctly.  The steps I did were:

1)  went to my dockers and chose "stop" for the current emby docker.

2)  clicked on docker repositories and pasted in "https://github.com/M...templates/emby"

3) went back to docker tab and clicked "add container", then "select a template" - "emby" -  "embyserver"

4) it autopopulated in the settings I had from the previous emby server docker (/mnt/cache/appdata/emby for /config, and /mnt for /mnt)

5) clicked save and let it go.

6) started the docker and went to the webgui - and it wants to start from scratch (welcome to Emby, create users, etc)

 

do I really have to recreate all of my users and custom settings etc?   I thought with the same volume mappings it would find my old configs?

 

also, why do both the old and new templates point toward

Container Page: https://registry.hub...mby/embyserver/

this seems to mean they are the same thing ?

 

thanks for the help,

 

(btw, I have not deleted my old emby docker yet....just have it "stopped")

 

I think it is working now - missed something simple.  The new docker defaults for volume mapping was just *almost* the same.  Except it used lowercase emby and I previously had Emby for the appdata/Emby directory.  Fixed the case and it detected my settings.  Sorry for the bother - maybe this helps someone else with this issue in the future.

Glad you have it working. The testing image was moved to the stable branch and so it replaced the old image.







Also tagged with one or more of these keywords: docker, tumbleweed, suse

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users