Any tips on running it under CoreOS ? about docker-cacti HOT 11 CLOSED

I have very first version of this docker image running in my production and works just fine. I'm using CoreOS Beta 440 as host OS.

run it using this command:
docker run -d --name cacti --net host polinux/cacti

then access it on http://server_ip/cacti

FYI Just updated. :)

from docker-cacti.

How do you handle the restart of containers on CoreOS when the server boots
up? Basically use start and stop of the named container?

2014-09-21 17:05 GMT-04:00 Przemysław Ożgo [email protected]:

Closed #1 #1.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from docker-cacti.

You create another service by following this example:
https://coreos.com/using-coreos/systemd/

Everything needed for this is in CoreOS documentation.

from docker-cacti.

I'm starting to get the hang of it. Let's say that I start a container
using directly your polinux/cacti, is it possible to rebase my running
container when I stop? When I did a pull of your cact (polinux/cacti)i, I
saw that I lost the tag and it reverted to an hex (I guess you recently
updated it):
dcba08f6b93d 280b0db317be "/install/bootstrap. 12
hours ago Up 2 hours 0.0.0.0:8080->80/tcp cacti

Ciao,
...David

Le 2014-09-22 02:47, "Przemysław Ożgo" [email protected] a écrit :

You create another service by following this example:
https://coreos.com/using-coreos/systemd/

Everything needed for this is in CoreOS documentation.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from docker-cacti.

Hi

Yes when you run pull polinux/cacti it will download latest image that was updated yesterday. :)

Whenever you do docker run you create a container using that image :)
Image will stay the same forever but the container will be changing inside.

If you need to login into your container you can run docker-enter command and then you are in your container.

Kind Regards

Przemyslaw Ozgo
+44 7740 814002
[email protected]

On 22 Sep 2014, at 16:20, David Lebel [email protected] wrote:

I'm starting to get the hang of it. Let's say that I start a container
using directly your polinux/cacti, is it possible to rebase my running
container when I stop? When I did a pull of your cact (polinux/cacti)i, I
saw that I lost the tag and it reverted to an hex (I guess you recently
updated it):
dcba08f6b93d 280b0db317be "/install/bootstrap. 12
hours ago Up 2 hours 0.0.0.0:8080->80/tcp cacti

Ciao,
...David

Le 2014-09-22 02:47, "Przemysław Ożgo" [email protected] a écrit :

You create another service by following this example:
https://coreos.com/using-coreos/systemd/

Everything needed for this is in CoreOS documentation.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub.

from docker-cacti.

2014-09-22 13:18 GMT-04:00 Przemysław Ożgo [email protected]:

Whenever you do docker run you create a container using that image :)

I guess it's a drawback of docker. Since the database and config for cacti
from your container is inside the container, updating my version of it to
reflect your modifications would require that I spin another container with
run without all my cacti config and database.

Ciao,
...David

// david lebel [email protected]
// http://www.lebel.org/
// https://keybase.io/lebel

from docker-cacti.

Exactly.

:)

Unfortunatelly thats what it is. :)

I have planned to work on dividing this into two dockers one with the database and one with cacti itself. But Now I’m busy with other projects so would need to leave it for now.

Kind Regards

Przemyslaw Ozgo
+44 7740 814002
[email protected]

On 22 Sep 2014, at 18:45, David Lebel [email protected] wrote:

2014-09-22 13:18 GMT-04:00 Przemysław Ożgo [email protected]:

Whenever you do docker run you create a container using that image :)

I guess it's a drawback of docker. Since the database and config for cacti
from your container is inside the container, updating my version of it to
reflect your modifications would require that I spin another container with
run without all my cacti config and database.

Ciao,
...David

// david lebel [email protected]
// http://www.lebel.org/
// https://keybase.io/lebel
—
Reply to this email directly or view it on GitHub.

from docker-cacti.

while teaching myself to dockerize cacti to use an external database, I did
hit a wall with spine. Since when linking container so the IP and port than
I need to use is variable (Ie. $MYSQL_PORT_3306_TCP_ADDR), I didn't find a
way to specify the host address in the config file, unless I'm able to use
variables in the way we call spine so we specify there the host address.

Till then, I'm using your container successfully.

Ciao,
...David

// david lebel [email protected]
// http://www.lebel.org/
// https://keybase.io/lebel

2014-09-22 13:58 GMT-04:00 Przemysław Ożgo [email protected]:

Exactly.

:)

Unfortunatelly thats what it is. :)

I have planned to work on dividing this into two dockers one with the
database and one with cacti itself. But Now I’m busy with other projects so
would need to leave it for now.

Kind Regards

Przemyslaw Ozgo
+44 7740 814002
[email protected]

On 22 Sep 2014, at 18:45, David Lebel [email protected] wrote:

2014-09-22 13:18 GMT-04:00 Przemysław Ożgo [email protected]:

Whenever you do docker run you create a container using that image :)

I guess it's a drawback of docker. Since the database and config for
cacti
from your container is inside the container, updating my version of it
to
reflect your modifications would require that I spin another container
with
run without all my cacti config and database.

Ciao,
...David

// david lebel [email protected]
// http://www.lebel.org/
// https://keybase.io/lebel
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from docker-cacti.

2014-09-26 17:49 GMT-04:00 David Lebel [email protected]:

MYSQL_PORT_3306_TCP_ADDR

Nevermind, there's a host entry in /etc/hosts with the proper IP, so, no
need to play with environment variables.

Ciao,
...David

// david lebel [email protected]
// http://www.lebel.org/
// https://keybase.io/lebel

from docker-cacti.

Ok, I forked your docker-cacti and made some modifications to it.

https://github.com/lebel/docker-cacti

I now have cacti running using both a datavolume (with /var/lib/cacti/rra
and /var/log/cact) and a mariadb running tutum/mariadb that I previously
imported a cactiuser and the .sql file until I fix that by detecting an
emty database and whatnot.

Also, I fixed that way you call apache and cron so they don't fork and stay
in the foreground so supervisord does its job properly.

Anyway, take a look at it.

Ciao,
...David

// david lebel [email protected]
// http://www.lebel.org/
// https://keybase.io/lebel

2014-09-26 21:26 GMT-04:00 David Lebel [email protected]:

2014-09-26 17:49 GMT-04:00 David Lebel [email protected]:

MYSQL_PORT_3306_TCP_ADDR

Nevermind, there's a host entry in /etc/hosts with the proper IP, so, no
need to play with environment variables.

Ciao,
...David

// david lebel [email protected]
// http://www.lebel.org/
// https://keybase.io/lebel

from docker-cacti.

@lebel Addding those volumes for persistency is really helpful. Thanks!

from docker-cacti.