plainblack.com
Username Password
search
Bookmark and Share

    
Goto page «Previous Page   1 2    Next Page»

wG8 Docker image

User scottwalters
Date 9/2/2015 3:25 pm
Views 5369
Rating 1    Rate [
|
]
Previous · Next
User Message
scottwalters


Hi all,

I created a wG8 Docker image and put it on Docker Hub:

https://hub.docker.com/r/scrottie/webgui8/

The install instructions in the README.md briefly explain how to set this up:

https://github.com/AlliumCepa/webgui/blob/master/README.md

The AlliumCepa branch was created to give more commit bits to more people.  It is hoped that it will eventually be rolled back in to the main branch.  Recent wG8 work has been done in AlliumCepa.

This is a testing release.  Image::Magick was replaced with Imager.  The Docker file was built on top of the minimal Debian image using the new installer script, but not without problems.  The Docker image is not yet automatically being re-built from changes to the GitHub repo.  Help is always appreciated!

Please test and report any problems in this Docker image of wG8.

--- (Edited on 9/2/2015 3:25 pm [GMT-0500] by scottwalters) ---



Back to Top
Rate [
|
]
 
 
martien

Hi Scott,

I should like to try it with Docker, but I couldn't pull the image:

mld:~ # docker pull scrottie/webgui8
Using default tag: latest                                                                                                                                       
Pulling repository docker.io/scrottie/webgui8                                                                                                                   
Tag latest not found in repository docker.io/scrottie/webgui8

Since Docker is new to me:
Should the image work on a non-debian Linux?


Thanks,

Martien

--- (Edited on 2015-09-22 12:55 [GMT+0200] by martien) ---



Back to Top
Rate [
|
]
 
 
scottwalters

                                                                                                       

Tag latest not found in repository docker.io/scrottie/webgui8



Hi Martien,

I'm new to Docker as well.  It looks like I misunderstood how the 'latest' tag works.  I thought it was a meta-tag that found the newest image, but it's just a default tag.  The actual tag of the image was 'testing5', by the way.  I uploaded it again with the tag 'latest'.  Please try again and let me know if it works for you.

Also, Docker images are mini-Linux installs (or not so mini ones) that bundle all of the dependencies for the service they provide.  If you have Docker installed, and it's new enough, you should be able to run any Docker image without installing any additional dependencies on your local system.

The downside of course is that the Docker images have to be kept up to date, but there are tools for automating the building of them from github (on my todo list).

Thanks,
-scott

--- (Edited on 9/22/2015 3:27 pm [GMT-0500] by scottwalters) ---



Back to Top
Rate [
|
]
 
 
martien

Hi Scott,

 The actual tag of the image was 'testing5', by the way.  I uploaded it again with the tag 'latest'.  Please try again and let me know if it works for you.

"docker pull scrottie/webgui8:testing5" did the pull

The first start:

docker run  -p 80:80 scrottie/webgui8:testing5

didn't work. I got a firewall (iptables) problem, which seems to be a Docker issue

Without a firewall and restarting docker, WebGUI started!!!

Thanks, Martien

--- (Edited on 2015-09-22 23:59 [GMT+0200] by martien) ---



Back to Top
Rate [
|
]
 
 
bartjol

As far as I can see on https://hub.docker.com/r/scrottie/webgui8/ the tag is testing and not latest.

On the debian question, I suppose it might, but it is probably depending on the installed packages on the system, so you might miss dependancies that are default on debian, but not on Linux distro X.

--- (Edited on 22-September-2015 14:15 [GMT+0200] by bartjol) ---



Back to Top
Rate [
|
]
 
 
martien

Hi Bart,

As far as I can see on https://hub.docker.com/r/scrottie/webgui8/ the tag is testing and not latest.

I also tried (didn't mention):

mld:~ # docker pull scrottie/webgui8:testing
Pulling repository docker.io/scrottie/webgui8
Tag testing not found in repository docker.io/scrottie/webgui8

On the debian question, I suppose it might, but it is probably depending on the installed packages on the system, so you might miss dependancies that are default on debian, but not on Linux distro X.

I'll give it a try

--- (Edited on 2015-09-22 14:29 [GMT+0200] by martien) ---



Back to Top
Rate [
|
]
 
 
scottwalters

The docs at on the dockerhub page that say docker run -t -i -p 80:80 scrottie/webgui8:testing are slightly wrong with respect to the tag.  I'll have to tidy up all of the tag references.

As far as iptables, no idea there.  It should block incoming connections, not prevent docker images from starting.  It also probably shouldn't be blocking port 80 on lo0.  Let me know if you figure out why that was keeping it from starting and I'll see if I can work around it.

--- (Edited on 9/22/2015 5:31 pm [GMT-0500] by scottwalters) ---



Back to Top
Rate [
|
]
 
 
martien


As far as iptables, no idea there.  It should block incoming connections, not prevent docker images from starting.  It also probably shouldn't be blocking port 80 on lo0.  Let me know if you figure out why that was keeping it from starting and I'll see if I can work around it.

It seems to be OS-dependent.

[https://github.com/docker/docker/issues/1871]

I my (SuSE) case, I have to find a possibility to adapt the fw-rules or define them myself.
Perhaps https://github.com/gdm85/docker-fw could help, but I don't get it compiled.

--- (Edited on 2015-09-23 10:01 [GMT+0200] by martien) ---



Back to Top
Rate [
|
]
 
 
martien


As far as iptables, no idea there.  It should block incoming connections, not prevent docker images from starting.  It also probably shouldn't be blocking port 80 on lo0.  Let me know if you figure out why that was keeping it from starting and I'll see if I can work around it.

Meantime it works without problems. The only thing is, that the firewall doesn't reset to the original state if I stop Docker without trouble.

Docker seems to be exciting for getting a first running system, without touching existing WebGUI's.
For managing/controlling, Stackengine seems to be a nice tool.
For updates of source code (from svn, perforce or git), certainly something has to be done.

However, the WebGUI8 image doesn't allow to make changes.

I can login, use the admin, but saving changes doesn't work.
Any idea why?

--- (Edited on 2015-10-22 23:29 [GMT+0200] by martien) ---



Back to Top
Rate [
|
]
 
 
scottwalters

Hi martien,

As for code updates, there are a couple of options.  Docker images are meant to be modular and essentially disposible, so the "normal" Docker approach would be to download new images as they're released.

If a container includes enough of Linux (which the wG ones do), you can also run 'bash' inside of them, and use that to make updates, such as doing git checkouts or downloading the repo .zip from github:

docker run -t -i scrottie/webgui /bin/bash

(Or attach to an existing instance and do that.)

After making any changes, you have to explicitly write them out to a new container image or else they're lost.  (And then every time you do that, it adds another layer on top of the unionfs stack, which is sloppy and slow and can quickly hit the max number of layers limit.  Five or so layers is the recommended working number.)

As for changes being lost on restart, you need to resume a previous instance instead of creating a new instance.  'docker run' creates a new instance.  It's easy (as intended by Docker) to have lots of instances running, or instances started but then stopped.  Instances are cheap.

The Docker image is built so that /usr/var, where MySQL keeps its data, is persisted for each instance.

'docker ps' lists all of the instances you've created.  'docker ps -a' shows the stopped ones.  Etc.

'docker stop' and 'docker start' work on those instances to stop and start them.

The Docker images would ideally automatically build new versions when code is committed to github, but I haven't automated that yet.  That doesn't automate actually downloading the Docker containers, or running upgrades.  I haven't looked in to how to do that.

If you are already doing that (re-starting existing instances rather than generating new ones) and it's losing your data, give me a transcript of exactly what you're doing when this happens and I'll look in to it, but off the top of my head, I'm guessing that that's the most likely explanation.

Thank you for testing that stuff.  Though it's far from perfect, I can see the appeal of Docker.

And sorry for the lack of commits lately.  I'm refilling coffers again but hope to take another break and resume soon here, as soon as I can wrap this up.

--- (Edited on 10/22/2015 5:02 pm [GMT-0500] by scottwalters) ---



Back to Top
Rate [
|
]
 
 
     Goto page «Previous Page   1 2    Next Page»



© 2017 Plain Black Corporation | All Rights Reserved