Can you use Docker Hub repositories?

[DigitalRobot]

I'm kinda new to Unraid (and Docker), only just set it up at the weekend. I added some repositories from the Unraid ones listed here, however when I tried to include repositories from Docker Hub (https://hub.docker.com/) they don't appear in the templates list.

 

Is this possible or am I missing something obvious?

[Squid]

Easy answer would be to install Community Applications  https://lime-technology.com/forum/index.php?topic=40262.0.  Then you can forget altogether about populating the repositories under the docker tab, and you can also optionally search for and add any app listed on dockerHub.

 

Longer answer would be to keep using repositories (which IMO is an ancient and outdated way of handling apps on unRaid - and ass-backwards compared to how CA does it), and then manually populate the template if you want to add another app from dockerHub

[DigitalRobot]

Thanks, it works well. I'm a bit confused over which repositories it uses (it has some of the ones from Docker Hub but not others), is there a way to add custom repositories to it?

[Squid]

It grabs a list of all of the currently available templates available for unRaid.  It can also optionally add any app you find on dockerHub (turn on dockerhub searches in its settings)

 

"Repositories" in CA parlance is the same as unRaid uses it -> a collection of unRaid templates. 

 

A Repository in dockerHub parlance is what CA would refer to as an Application (and unRaid would refer to as a Container).

[Squid]

And as a general rule if trying to decide between a generic app available on dockerHub, and an equivalent available natively through CA, you should pick the native one.

 

It'll be better supported under unRaid, and you're going to be able to have some sort of guarantee that it will actually work (a significant percentage of apps on dockerHub are half finished)

 

[itimpi]

And as a general rule if trying to decide between a generic app available on dockerHub, and an equivalent available natively through CA, you should pick the native one.

 

It'll be better supported under unRaid, and you're going to be able to have some sort of guarantee that it will actually work (a significant percentage of apps on dockerHub are half finished)

Not sure I always agree with this although it is often true.  It probably depends on the relationship between the docker developer and the app developers.    A good example of an exception is the ownCloud docker where you can get an official one created and maintained by the ownCloud developers, rather than one built by an unRAID developer.  In this case support for the official ownCloud one is likely to be better.

[Squid]

And as a general rule if trying to decide between a generic app available on dockerHub, and an equivalent available natively through CA, you should pick the native one.

 

It'll be better supported under unRaid, and you're going to be able to have some sort of guarantee that it will actually work (a significant percentage of apps on dockerHub are half finished)

Not sure I always agree with this although it is often true.  It probably depends on the relationship between the docker developer and the app developers.    A good example of an exception is the ownCloud docker where you can get an official one created and maintained by the ownCloud developers, rather than one built by an unRAID developer.  In this case support for the official ownCloud one is likely to be better.

Fair enough...  I was speaking in general terms