[OUTDATED] Extended Docker configuration page

[gfjardim]

Tom, can you please add GIT to the next beta? The GH api limit kills my code everytime.

[limetech]

The my-* files are runtime variables. They store the user customizations of the original templates. For users, it's more important to keep those my-* files safe then the rest of the content. Why, you could ask me? Because:

 

1) They are used to update containers. When we update a container, in fact we're removing it, pulling the new image and recreating the container with the same runtime variables, stored on the my-* templates.

 

2) The user can remove all containers and images, and latter he can restore any previous container with only 4 clicks, using the same values as before. He can update the whole server, plug the flash drive on it, and again recreate all containers exactly as they were.

 

Because of that, I think we should keep them in the flash drive.

 

Ok I'm fine with that, good reasoning.

 

So really the only addition to /var/lib/docker is unraid-autostart correct?

 

 

[gfjardim]

The my-* files are runtime variables. They store the user customizations of the original templates. For users, it's more important to keep those my-* files safe then the rest of the content. Why, you could ask me? Because:

 

1) They are used to update containers. When we update a container, in fact we're removing it, pulling the new image and recreating the container with the same runtime variables, stored on the my-* templates.

 

2) The user can remove all containers and images, and latter he can restore any previous container with only 4 clicks, using the same values as before. He can update the whole server, plug the flash drive on it, and again recreate all containers exactly as they were.

 

Because of that, I think we should keep them in the flash drive.

 

Ok I'm fine with that, good reasoning.

 

So really the only addition to /var/lib/docker is unraid-autostart correct?

 

Beta8:

$dockerManPaths = array(
'plugin'         => '/usr/local/emhttp/plugins/dockerMan',
'autostart-file' => '/var/lib/docker/unraid-autostart',
'update-file'    => '/tmp/dockerUpdateStatus.json',
'template-repos' => '/boot/config/plugins/dockerMan/template-repos',
'templates-user' => '/var/lib/docker/unraid-templates',
'templates-stor' => '/usr/local/emhttp/plugins/dockerMan/templates',
'images-ram'     => '/usr/local/emhttp/plugins/dockerMan/assets/images',
'images-stor'    => '/var/lib/docker/unraid/images',
);

 

Beta9:

$dockerManPaths = array(
'plugin'         => '/usr/local/emhttp/plugins/dockerMan',
'autostart-file' => '/var/lib/docker/unraid-autostart',
'update-file'    => '/tmp/dockerUpdateStatus.json',
'template-repos' => '/boot/config/plugins/dockerMan/template-repos',
'templates-user' => '/boot/config/plugins/dockerMan/templates-user',
'templates-stor' => '/boot/config/plugins/dockerMan/templates',
'images-ram'     => '/usr/local/emhttp/plugins/dockerMan/assets/images',
'images-stor'    => '/boot/config/plugins/dockerMan/images',
);

 

Is this it?

[limetech]

Is this it?

Perfect!

[trurl]

I am going in beta8 now. Thanks for the LogitechMediaServer docker. Got my other dockers going too, except for the most important one.

 

Unfortunately, it looks like gfjardim/transmission is not on the docker hub now. I really need to get my torrents seeding again. I see it is in the new templates, but there is nothing on the docker hub for it to get.

 

Will you be putting it back up soon?

 

Edit:

Looks like you put it back up just a few minutes after I posted this. All working now. Thanks

[gfjardim]

I am going in beta8 now. Thanks for the LogitechMediaServer docker. Got my other dockers going too, except for the most important one.

 

Unfortunately, it looks like gfjardim/transmission is not on the docker hub now. I really need to get my torrents seeding again. I see it is in the new templates, but there is nothing on the docker hub for it to get.

 

Will you be putting it back up soon?

 

Edit:

Looks like you put it back up just a few minutes after I posted this. All working now. Thanks

 

I put it back because of you. I recently consolidate all my containers in one GitHub repo, and made a typo when reinsert the Transmission container. Thanks for figuring it out.

[JM2005]

I am running your latest beta 8 plugin and noticed I am only see 2 dockers they are showing they are updated as the rest are showing N/A again.  Didn't know is this working or not since the updates.

 

Thanks again for your hard work!!

[deaerator]

I am running beta 8, I have two instances of docker plugins running at the same time.  Is this normal.  I do notice that states its "Built in" and the other gives me the option to remove.

[gfjardim]

I am running beta 8, I have two instances of docker plugins running at the same time.  Is this normal.  I do notice that states its "Built in" and the other gives me the option to remove.

 

This is a bug that I already corrected.

[deaerator]

I am running beta 8, I have two instances of docker plugins running at the same time.  Is this normal.  I do notice that states its "Built in" and the other gives me the option to remove.

 

This is a bug that I already corrected.

 

Being a linux noob, how do i correct this.

[nacat78]

just finished doing an update to dockerman.plg a few minutes ago - now extensions page no longer works.....

 

just shows

Parse error: syntax error, unexpected '=>' (T_DOUBLE_ARROW) in /usr/local/emhttp/plugins/dockerMan/dockerClient.php on line 115 

[Spydawg]

same

 

[gfjardim]

just finished doing an update to dockerman.plg a few minutes ago - now extensions page no longer works.....

 

just shows

Parse error: syntax error, unexpected '=>' (T_DOUBLE_ARROW) in /usr/local/emhttp/plugins/dockerMan/dockerClient.php on line 115 

 

That's what happens when you click like crazy on that Update button! 

 

[gfjardim]

[glow=red,2,300]UPDATE:[/glow]

 

Version 2014.09.06-1:

- Loads of mods  .

 

Ok, guys, I will explain what has been done in this release. 

 

Tom approached me about two weeks ago, informing that this plugin would be a part of the unRAID core (he asked, I said yes!, etc...).

 

Then he explained to me that, in his vision, apps should have an icon, and that the templates must be treated as add-ons. No templates should be distributed with unRAID. But the time was short, and beta8 was released without icons and with a limited set of templates.

 

Well, a lot o development was done this week, the plugin has being broken and fixed all the time (thanks for the patience), but here we stand. Now the plugin have both icons and banners (I don't know if Tom will retain the banners, tho). But the templates issue hasn't being addressed until now.

 

From now on, No templates will be distributed with this plugin or unRAID by default. What does this mean?

 

1) Template repositories must be added by the user;

2) Users can add template repositories on the proper field;

 

To help the transition, I've created a template repository here:

 

https://github.com/gfjardim/docker-containers/tree/templates

 

After update the plugin, a new field will appear on the Docker extension page. Add this address there and click Save.

 

Developers are asked to create their own template repositores. Other way of distributing templates is to host a [conteiner-name].xml file with the container itself and distribute the GitHub address, assuming that it's the only .xml file in there.

 

Be advised that this is all very new, so expect some hiccups.

 

Thanks for your support.

[Spydawg]

Thanks!

[limetech]

Version 2014.09.06-1:

- Loads of mods  .

NICE WORK! 

 

(I don't know if Tom will retain the banners, tho).

The banners are cool!  We will retain 

 

From now on, No templates will be distributed with this plugin or unRAID by default.

A future release may include a set of templates from a limetech repo by default.

 

[jonp]

gf,

 

This is great work on your part and we're glad to see this continued advancement to dockerMan!  What started off as a simple "start / stop" screen has since evolved into a masterful work that we're proud to have included with unRAID 6.  Thank you again!!

[abeksis]

Can I get an explanation of how to install the plugin? I installed under the old explanation, when I reboot the server, the config off the plugin gong

[JustinChase]

What started off as a simple "start / stop" screen has since evolved into a masterful work that we're proud to have included with unRAID 6.

 

Completely agree!

 

Perhaps the description needs updated now...

 

This is a very basic plugin currently used mainly to hook start up and tear down of Docker containers with array Start/Stop events.

 

Uh, hardly.

[gfjardim]

installed the new plugin for beta 8

 

and I get this

 

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dockerMan/dockerClient.php on line 545
Couldn't create socket: [2] No such file or directory
Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dockerMan/dockerClient.php on line 545

 

Well, seems like you have a defunct docker on your system; the process still there, so the page is shown, but the socket used to retrieve information isn't.

 

Try stopping and starting docker.

[gfjardim]

UPDATE:

Version 2014.09.06-2:

- Improved the update detection routine;

 

The update detection routine I was using was based on downloading and extracting build information from the Docker Hub site. This was a slow process with two pages needed to be downloaded, and there was always the chance of a minor layout change break everything. So I've studied the Docker Hub API documentation, and figure out a way to do the same, but just with the API's JSON response.

 

Now the part that interests you: all your update status is going to be invalidated, so to obtain a valid one again, you will need to update all your containers once, like you did the first time I introduce this feature.

 

By the way, I swear, guys, this is the last update of the day!

 

[deaerator]

I started from scratch, and now i have docker running and installed your plugin.  The extension page just keeps on telling me that it is "installing".

 

[JustinChase]

I started from scratch, and now i have docker running and installed your plugin.  The extension page just keeps on telling me that it is "installing".

 

the installing... doesn't go away, but it's finished.  Just go to the docker page, and you should see it working.

[deaerator]

I think its all working fine now.

 

Thank you

 

I appreciate everybody's hard work

[JustinChase]

UPDATE:

Version 2014.09.06-2:

- Improved the update detection routine;

 

The update detection routine I was using was based on downloading and extracting build information from the Docker Hub site. This was a slow process with two pages needed to be downloaded, and there was always the chance of a minor layout change break everything. So I've studied the Docker Hub API documentation, and figure out a way to do the same, but just with the API's JSON response.

 

Now the part that interests you: all your update status is going to be invalidated, so to obtain a valid one again, you will need to update all your containers once, like you did the first time I introduce this feature.

 

By the way, I swear, guys, this is the last update of the day!

 

I updated, removed 2 containers and images, then installed from my xml files.  Both still show N/A under update.  One of them (MovieGrabber) has always shown N/A, but the other (Deluge) used to work, but after this most recent update, it shows N/A still.