[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2021-11-28 Thread Ioan Eugen Stan (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17449970#comment-17449970
 ] 

Ioan Eugen Stan commented on OFBIZ-10407:
-

There are some things to solve in order to make a usable docker image for ofbiz:
 * script to initial load data when starting the ofbiz container app
 * a way to load data in the system - the rest plugin seems to be a good way to 
do this - Would be great to have this plugin included in main source code
 * a way to install plugins on the base image - right now the only way to have 
plugins in the docker image is to rebuild the image with the plugins - because 
ofbiz does not have a way to add binary plugins on top of an ofbiz image

I recommend raising some issues to solve these. 

I have a branch and github action that builds docker images: 
[https://github.com/ieugen/ofbiz-framework/actions] with rest API plugin.  

Docker images are published [https://hub.docker.com/r/ieugen/ofbiz] 
Kubernetes chart is published [https://github.com/ieugen/charts 
|https://github.com/ieugen/chartsb]

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Assignee: Michael Brohl
>Priority: Major
>  Labels: DevOps
> Attachments: OFBIZ-10407_dockerfile.patch, docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-12-01 Thread Ioan Eugen Stan (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241520#comment-17241520
 ] 

Ioan Eugen Stan commented on OFBIZ-10407:
-

Hi,

I would like to add my (outside) experience to this.

I've been working with Docker and Kubernetes for the past 3+ years.

Docker images should be simple and contain as little layers as possible.

This makes maintenance and deployment simple to do and manage over time.

Looking at OFBiz - I see there is:
 * ofbiz-framework - which should be static more or less and only changes with 
new releases.
 * ofbiz-plugins - which can vary from deployment to deployment - they can be 
updated more often.
 * configuration files - can be updated even more often then plugins
 * database (external or embedded) - external state
 * client data - most frequent changes - external state, like DB.

The strategy I employed with good results is to build a new docker image when 
new releases happen and use volumes for configuration and external state.

Databases are usually deployed as a seprate container.

Translating this to OFBiz - build a binary distribution that is the app and in 
Dockerfile, just unpack that binary.

Use a java-jre image for running the app.

This will keep the image simple to update and manage (bugfix, debug) and the 
attack surface small.

 

You can use docker to build the entire project from source, but IMO that should 
be done using docker multi-stage builds 
[https://docs.docker.com/develop/develop-images/multistage-build/] .

The final docker build stage build should just copy the binary into it's place 
from previous build.

For the plugins, they can also be unpacked/copied into place or a docker volume 
can be created/mounted in place and copied there if they need to be managed as 
state (not recommended).

For configurations - they can be copied in place once the docker image is build 
- not that good since you want to change configs over time.

I usually mount configs from host system or configmap in Kubernetes.

 

The setup I described above works best if OFBiz publishes artifacts for 
framework and plugins.

I did not see anything published on central 
[https://search.maven.org/search?q=ofbiz] .

If the artifacts are published then we can create a gradle project that can be 
used as a STARTER.

This STARTER project will depend on framework-XX.YY and on plugins-abc-13.23.

It will be able to download the specified versions and bundle them together in 
a binary distribution - zip or tar.gz.

We can then build a docker image from that binary distribution.

Since gradle can also depend on other gradle subprojects (dependency 
":my-plugin-project"), people can also use this setup for local plugin 
development / testing.

People can copy the starter and build production distributions with the 
dependencies they want / need.

 

 

 

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Assignee: Michael Brohl
>Priority: Major
>  Labels: DevOps
> Attachments: OFBIZ-10407_dockerfile.patch, docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-13 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058933#comment-17058933
 ] 

Pierre Smits commented on OFBIZ-10407:
--

That appears to be bidirectional.

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Assignee: Michael Brohl
>Priority: Major
>  Labels: DevOps
> Attachments: OFBIZ-10407_dockerfile.patch, docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-13 Thread Michael Brohl (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058931#comment-17058931
 ] 

Michael Brohl commented on OFBIZ-10407:
---

Always a pleasure to work with you Pierre.

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Assignee: Michael Brohl
>Priority: Major
>  Labels: DevOps
> Attachments: OFBIZ-10407_dockerfile.patch, docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-13 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058922#comment-17058922
 ] 

Pierre Smits commented on OFBIZ-10407:
--

Since you made this into something bigger than a simple contribution because of 
your complaints and dictats, bring it to the dev ml.

In the meanwhile, I have been working on a solution that will enable users 
(developers/adopters/etc.) to generate containers, that either will be based:
* on a branch (trunk or whatever) without plugins and git-aware
* on a branch with plugins git-aware
* on a release without plugins
* on a release with plugins

And for the latter two I am looking at how to have it production-ready.

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Assignee: Michael Brohl
>Priority: Major
>  Labels: DevOps
> Attachments: OFBIZ-10407_dockerfile.patch, docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-13 Thread Michael Brohl (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058902#comment-17058902
 ] 

Michael Brohl commented on OFBIZ-10407:
---

Hi everyone,

any thoughts about the provided Docker files and the question if we want to 
have them in the codebase?

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Assignee: Michael Brohl
>Priority: Major
>  Labels: DevOps
> Attachments: OFBIZ-10407_dockerfile.patch, docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-09 Thread Michael Brohl (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054822#comment-17054822
 ] 

Michael Brohl commented on OFBIZ-10407:
---

I've added a basic dockerfile which adresses the mentioned issues and provides 
parameterization for building different images for trunk and release branches.

It's build on the Adopt Open JDK images with Ubuntu 18.04 LTS and latest Adopt 
Open JDK 8 release. Usage is documented in the dockerfile.

It does not provide production configuration or database choice which should be 
adressed when the community thinks it would be a good idea to place OFBiz 
Docker images on docker hub.

What do you think?

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Assignee: Michael Brohl
>Priority: Major
>  Labels: DevOps
> Attachments: OFBIZ-10407_dockerfile.patch, docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-08 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054398#comment-17054398
 ] 

Pierre Smits commented on OFBIZ-10407:
--

The provided Dockerfile may be derived from the version in another project, but 
is tailored to OFBiz testing and evaluation. You should let that argument go, 
[~mbrohl].

Having different images on docker hub for all OFBiz variants (based on choice 
of production grade RDBMS and with/without plugins) requires some serious 
parameterisation.

The project is not there yet.

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Priority: Major
>  Labels: DevOps
> Attachments: docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-08 Thread Michael Brohl (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054366#comment-17054366
 ] 

Michael Brohl commented on OFBIZ-10407:
---

The recommended distro for Open JDK is Adopt Open JDK which is not just another 
download location. Maybe we should make it more clear in the README but it 
should not prevent us from using it in our official Repo/dists.

Since the Docker image(s) are just for testing and evalution purposes as you 
stated, it should not matter that the code is installed in another directory 
(/opt, which is not so unusual for the installation of additional software 
packages).

I don't see any reason to install additional software packages which are not 
needed so why not remove them to a minimum? It makes the build time shorter and 
maintenance easier.

I'll work on an alternative which will address my concerns so that we will have 
a selection to chose from.

As for the location to provide them, we should hear what others have to say. I 
also imagine to provide the different images on the docker hub like many other 
Apache projects do so it might be reasonable to think that way.

 

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Priority: Major
>  Labels: DevOps
> Attachments: docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-08 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054356#comment-17054356
 ] 

Pierre Smits commented on OFBIZ-10407:
--

Thank you, [~mbrohl], for your feedback.


 * Re "we should use the Adopt Open JDK as listed in the requirements"
The readme.adoc in the repository on Github states
??The only requirement to run OFBiz is to have the Java Development Kit (JDK) 
version 8 installed on your system??
and provides a link to an advised download location. However, many Linux 
distros (including Ubuntu) provide OpenJDK binaries ready to use. So there is 
no need to do it differently;
* Re "xplicit Java installation can be removed by directly selecting the right 
Adopt Open JDK Docker image"
The Adopt Open JDK Docker image puts the OpenJDK code at a different location 
than what is grown a defacto standard in Linux distros. We should not follow 
this approach.
* Re "he used Ubuntu is outdated, we should use the 18.04 LTS release"
This has been corrected in an update to the PR
* Re "what about the Apache Yetus comment, seems to belong to another Docker 
image?"
This has been corrected in an update to the PR
* Re "the setup seems to add/install more than is needed"
Proposed Dockerfile is intended for testing and evaluation purposes, not for 
running a production setup where some of the added packages may not be desired. 
For now, I suggest to go with it as it is.

Regarding your other thoughts on using Dockerfiles for releases and moving it 
outside of the codebase.
A release where this is incorporated is still far into future. But you're 
correct: before we arrive on that moment this should be addressed. However, 
mature projects (visavis generating docker images) tend to have a CI process in 
play that ensures that images generated automatically use the code based on 
either branch or tag. We're not there yet. 

Having Dockerfile outside of the codebase has some negative side effects:
* we add additional complexity which needs to be communicated and maintained
* we add additional complexity in CI processes
For now I suggest the projects goes with this as it is, and as it matures it 
can decide where the favourable location should be.





> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Priority: Major
>  Labels: DevOps
> Attachments: docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-07 Thread Michael Brohl (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054214#comment-17054214
 ] 

Michael Brohl commented on OFBIZ-10407:
---

A few remarks for the pull request:
 * we should use the Adopt Open JDK as listed in the requirements
 * the setup seems to add/install more than is needed
 * what about the Apache Yetus comment, seems to belong to another Docker image?
 * the used Ubuntu is outdated, we should use the 18.04 LTS release
 * explicit Java installation can be removed by directly selecting the right 
Adopt Open JDK Docker image which makes also the ubuntu selection obsolete and 
would make the dockerfile smaller

A general thought: the provided dockerfile is targeted to the framework/plugins 
trunk which is ok for the trunk version. For the releases, we would need 
release specific versions. It would be confusing if you download a release 
package and the docker image would point to trunk.

Which brings me to the question if we better provide the dockerfile outside of 
the codebase?

 

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Priority: Major
>  Labels: DevOps
> Attachments: docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2020-03-04 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051116#comment-17051116
 ] 

Pierre Smits commented on OFBIZ-10407:
--

With PR#43 I have submitted a more simplified patch, that will help potential 
adopters and contributors evaluate our complete product in a contained 
environment. 

Build instruction:
docker build -t ofbiz/trunk:latest -f Dockerfile .

To run:
docker container run -ti -p 8009:8009 -p 8443:8443  --name OFBiz-Test 
ofbiz/trunk:latest



> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Hans Bakker
>Assignee: Pierre Smits
>Priority: Major
>  Labels: DevOps
> Attachments: docker.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
>  and after about 30 seconds it can be show in the browser under:
>  [https://0.0.0.0/catalog/control/main]
>  the image can be created by executing this command in the ofbiz root when 
> the patch is applied:
>  docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>   
> see the discussion in the mailinglist at 
> https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2018-05-17 Thread Jacques Le Roux (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478658#comment-16478658
 ] 

Jacques Le Roux commented on OFBIZ-10407:
-

Hi Hans,

Please put a link to the discussion in user ML in the description, thanks

Also there was already this discussion about a 16.11.01 docker image: 
https://markmail.org/message/fceytjfqss3qamko

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Hans Bakker
>Priority: Major
> Attachments: docker.patch
>
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
> and after about 30 seconds it can be show in the browser under:
> [https://0.0.0.0/catalog/control/main]
>  
> the image can be created by executing this command in the ofbiz root when the 
> patch is applied:
> docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2018-05-17 Thread Deepak Nigam (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478568#comment-16478568
 ] 

Deepak Nigam commented on OFBIZ-10407:
--

I personally liked the idea of using docker image very much as it is the demand 
of the industry today, but yes we need to work inline with the community.

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Hans Bakker
>Priority: Major
> Attachments: docker.patch
>
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
> and after about 30 seconds it can be show in the browser under:
> [https://0.0.0.0/catalog/control/main]
>  
> the image can be created by executing this command in the ofbiz root when the 
> patch is applied:
> docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2018-05-16 Thread Hans Bakker (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478547#comment-16478547
 ] 

Hans Bakker commented on OFBIZ-10407:
-

Yes we need newer copies of these filesor add a script to modify them as 
was done with entityrngine.properties.further the changeurl.sh was copied 
by accident and it is questionable if the change url part of initStart is 
required

let first let the community decide if this is acceptable before we put more 
work in this,.
 

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Hans Bakker
>Priority: Major
> Attachments: docker.patch
>
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
> and after about 30 seconds it can be show in the browser under:
> [https://0.0.0.0/catalog/control/main]
>  
> the image can be created by executing this command in the ofbiz root when the 
> patch is applied:
> docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2018-05-16 Thread Deepak Nigam (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478540#comment-16478540
 ] 

Deepak Nigam commented on OFBIZ-10407:
--

Thanks for the detailed information [~hansbak] . Now, cache.properties file is 
making some sense to me but if we talk about the trunk (in Dockerfile also, we 
are taking checkout from trunk), there is a change in theme pattern. So we 
should check the utility of widget.properties file once again.

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Hans Bakker
>Priority: Major
> Attachments: docker.patch
>
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
> and after about 30 seconds it can be show in the browser under:
> [https://0.0.0.0/catalog/control/main]
>  
> the image can be created by executing this command in the ofbiz root when the 
> patch is applied:
> docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2018-05-16 Thread Hans Bakker (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478370#comment-16478370
 ] 

Hans Bakker commented on OFBIZ-10407:
-

I changed the priority to major, because installing demo systems (yes even the 
ofbiz dmo version) should be done with docker to follow these important 
software developments.
Ofbiz also should , as all major open source systems do, provide an official 
docker image with every release.
 

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Hans Bakker
>Priority: Major
> Attachments: docker.patch
>
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
> and after about 30 seconds it can be show in the browser under:
> [https://0.0.0.0/catalog/control/main]
>  
> the image can be created by executing this command in the ofbiz root when the 
> patch is applied:
> docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2018-05-16 Thread Hans Bakker (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478359#comment-16478359
 ] 

Hans Bakker commented on OFBIZ-10407:
-

Thanks Deepak for your comments.

Yes in GrowERP we are using OFBiz-16 and these files are enabling cache within 
ofbiz. It will copy these files into the ofbiz system when the dockerimage is 
starting up.

This initial patch for ofbiz is welcoming comments as much as possible because 
docker not only is the choice for running a system in production but also to do 
OS independent software development.

For your information we are using the docker-machine command to automatically 
install a docker environment on AWS on a 4 processor 16Gb instance en running 9 
small ofbiz/growerp instances on it with excellent performance. examples: 
antwebsystems.com, productfromthailand,com growerp.com growerpdemo.com

I think that the docker production environment is much better than the tenant 
function in OFBiz and that the tenant function should be removed.

Regards,

Hans
 

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Hans Bakker
>Priority: Minor
> Attachments: docker.patch
>
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
> and after about 30 seconds it can be show in the browser under:
> [https://0.0.0.0/catalog/control/main]
>  
> the image can be created by executing this command in the ofbiz root when the 
> patch is applied:
> docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system

2018-05-16 Thread Deepak Nigam (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477255#comment-16477255
 ] 

Deepak Nigam commented on OFBIZ-10407:
--

Hi [~hansbak], thanks for taking the step towards dockerization of OFbiz. I am 
able to setup OFBiz on my local machine by the running the docker command 
provided by you.

I reviewed the docker.patch also. In this, Dockerfile and other scripts are 
looking good to me, but I didn't understand the utility of cache.properties and 
widget.properties files. It seems these are from an older version of OFBiz.

Can you please provide some information about the utility of these properties 
in this dockerization effort?

> create a docker image from the ofbiz system
> ---
>
> Key: OFBIZ-10407
> URL: https://issues.apache.org/jira/browse/OFBIZ-10407
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Hans Bakker
>Priority: Minor
> Attachments: docker.patch
>
>
> Attached an initial docker version from OFBiz copied from our GrowERP 
> production system translated to svn repositories.
> I propose to create a docker directory in the ofbiz framework root of which a 
> patch is attached.
> The image result is stored in hub.docker.com under the name ofbiz/full-trunk.
> It can be started in a docker environment with the following command:
> docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk
> and after about 30 seconds it can be show in the browser under:
> [https://0.0.0.0/catalog/control/main]
>  
> the image can be created by executing this command in the ofbiz root when the 
> patch is applied:
> docker build -t ofbiz/full-trunk docker
> the password to the ofbiz account at hub.docker.com will be supplied upon 
> request.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)