Fabric3 Containerization

[Tomáš Fecko]

Hi,

what is the "official" state of fabric3 containerization? I know we are speaking about this for years and some of you are probably already using it have it containerized.

Is it the time to roll out official fabric3 docker containers to docker hub?

What are your ideas about this? What needs to be done to accomplish this?

Tomas

[Jim Marino]

Hi Tomas,

That's a good question. We are using Fabric3 in a containerized environment and I know of other projects with similar setups.

The way we have it working is for the automated build to use the F3 assembly plugin to create a custom image with our required extensions. This image is then rolled into a Docker image that is deployed to a Rancher cluster. For persistent storage, we have the F3 data directory mapped to a GlusterFS clustered file system. This allows us to move container images easily and preserve database files which are mapped from the F3 data directory.

I've copied Patrick who has set this (and other F3 environments up). We would be happy to discuss further in more detail.

One question I have for the Docker images would be how do we handle F3 extensions? Do you know of a way to have Docker files overlay each other? This way we could incrementally add extensions by having multiple Docker images form a union.

Jim

    

--
You received this message because you are subscribed to the Google Groups "fabric3" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabric3+unsubscribe@googlegroups.com.
To post to this group, send email to fab...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fabric3/37b561ee-671d-4bf0-9704-2c1993dc866c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Patrick Boos]

Currently we use a very simple approach to run it in a container. Basically we copy the whole image into a docker container that is based on java8. Then we have an entrypoint that just boots.

Dockerfile

FROM    java:8

COPY docker-entrypoint.sh /entrypoint.sh

# This copies the distribution image into /data/image (make sure the path to image/ is correct).

COPY image/ /data/image

# any environment variables you use

ENV F3_ENVIRONMENT=development

EXPOSE  8080

ENTRYPOINT ["/entrypoint.sh"]

docker-entrypoint.sh

#!/bin/bash

java \

 -Dnats \

 -jar /data/image/bin/server.jar \

 clone:vm

So basically nothing special yet that we do. In our build process we basically first build the image. Then in a second step we copy that image out to the "docker" build folder where the Dockerfile and docker-entrypoint.sh is located. There we build the docker image.

We would have to look into it, if there is a way to actually make this even easier and provide kind of a fabric3 docker image. But I wonder if it is actually needed, since the above way seems easy and stable enough to me.

Cheers,

Patrick

On Tuesday, December 20, 2016 at 11:03:12 PM UTC+1, Jim Marino wrote:

Hi Tomas,

That's a good question. We are using Fabric3 in a containerized environment and I know of other projects with similar setups.

The way we have it working is for the automated build to use the F3 assembly plugin to create a custom image with our required extensions. This image is then rolled into a Docker image that is deployed to a Rancher cluster. For persistent storage, we have the F3 data directory mapped to a GlusterFS clustered file system. This allows us to move container images easily and preserve database files which are mapped from the F3 data directory.

I've copied Patrick who has set this (and other F3 environments up). We would be happy to discuss further in more detail.

One question I have for the Docker images would be how do we handle F3 extensions? Do you know of a way to have Docker files overlay each other? This way we could incrementally add extensions by having multiple Docker images form a union.

Jim

    

On Mon, Dec 19, 2016 at 1:36 PM, Tomáš Fecko <tomas...@gmail.com> wrote:

Hi,

what is the "official" state of fabric3 containerization? I know we are speaking about this for years and some of you are probably already using it have it containerized.

Is it the time to roll out official fabric3 docker containers to docker hub?

What are your ideas about this? What needs to be done to accomplish this?

Tomas

--
You received this message because you are subscribed to the Google Groups "fabric3" group.

To unsubscribe from this group and stop receiving emails from it, send an email to fabric3+u...@googlegroups.com.