This plugin is now deprecated.  (I think that's a record for the shortest time a plugin has been active - ~10 hours)

 

My other plugin DockerSearch incorporates this along with offering a search engine for the docker registry http://lime-technology.com/forum/index.php?topic=38879.0

 

Here is a basic plug-in to create a docker XML template for any docker container on https://registry.hub.docker.com/.  (It began as just a proof of concept, but evolved enough that its worthwhile to post)

 

https://raw.githubusercontent.com/Squidly271/Docker2XML/master/Docker2XML.plg

 

It is basically automating LionelHutz' directions posted here: http://lime-technology.com/forum/index.php?topic=37732.msg349938#msg349938  Hopefully it will make life easier for some users to run "non-unRaided" docker containers.

 

After installing the plugin, there will be Docker2XML on the settings page.  Just paste the URL from the Docker Container's Information page into the dialog box, hit convert and an XML file will be created.  (You can load it from the Docker2XML list in the drop down when you add a container.)

 

http://i46.photobucket.com/albums/f109/squidaz/Untitled_zpsyg7izjff.png[/img]

 

Notes:

 

If there is only one port exposed, then the webUI section of the template will also be filled in.

 

The script has to make a few assumptions about sections that cannot be easily derived from the dockerfile.

• Priviledged will be set to false
  
• Network type will be set to Bridge
  
• Any additional environment variables (eg: EDGE) will be not be added, but these will be detailed in the Information section of the dockerfile
  
• A minority of dockerfiles do not have explicit EXPOSE or VOLUME settings in them.  While the script will not fail on these containers, there will be missing information in the PORTS section and the VOLUME section.
  

 

These settings can easily be changed for the template if it is determined that the assumption was incorrect.

 

 

It seems that there are hundreds of different ways that docker files can passthrough the exposed ports and volumes.  If you find a docker file that this script does not correctly handle, let me know.

 

Also, if docker hub does not show 4 tabs (Information, DockerFile, BuildDetails, Tags) then the script will also fail (The majority seem to show all those however)

Very interested to try this out!!  Nice work!!

Mostly a proof of concept right now.  I threw a wack of random dockerfiles at it and it seemed to create a template correctly, but I'm sure there are ones out there that it can't handle yet