We are trying to deploy Axelor to Kubernetes. Has anyone done a Helm Chart for it?
If you have a solid Helm chart, that would really be appreciated.
Failing that, a working docker-compose.yaml file, containing all of the elements of the complete all-in-one deployment, including database connectivity and all modules would enable us to create a helm chart ourselves.
Allowed by whom, sorry? You are not allowed to push to the repo? You are not allowed by your company? Axelor does not permit it? My apologies, I don’t understand.
Is there someone who can help us? Is there any way for us to get a working helm chart for Axelor?
Failing all of the above, as a last resort, perhaps you could write an article containing instructions for how to do this?
Any help you can provide would be very much appreciated.
Thank you Siddique. I will need to get one of my team to look at your article and try it out - I like the way you are using Git, that’s very interesting. Just as an aside, have you tested it recently? Are you certain it will still build?
Update: One of my team has been able to run the aio-erp image in docker and deploy that to K8s in the usual manner. However, as I am sure you are aware, the aio-erp image is 3 years old.
Here is the problem; we have tried to rebuild the aio-erp image ourselves, by following the instructions exactly as written at
This fails. I won’t include the failures here, because it is very easy to see how it fails by simply trying it for yourself - it takes about 5 minutes. The aio-base and aio-builder both fail, and no images are generated. This is unexpected behavior.
Can someone please let me know if this axelor-docker build failure issue can/will be fixed? This is actually becoming an urgent issue for us, as we need to make some major decisions around Axelor in the next few days. Should we cross Axelor off of our list of ERP solutions? We like Axelor very much, but if it has gone out of maintenance, which is unfortunately what this looks like, then that is important for us to know.
Thank you all for your hard work. Please let me know as soon as possible.
I will not let the Axelor down just for this reason, see docker repo is not maintained, but you can see we are using it, and how we are using is the industry best practice, so there are approaches to do things and we adopt the easiest one as being lazy naturally.
And to evaluate something directly k8s is not best practice, you can get any instance up with plain java 8 installed on that system.
I am hopeful you will chose Axelor as your next ERP, nothing is perfect or ideal, we have to mold it to our needs.
Hi Siddique and Axelor Team,
Siddique, again, thank you for your response. Happily, K8S is no longer the issue. The issue is that the axelor-docker project cannot be built into a new aio-erp image to replace the 3 year old one. If that can be done, all our problems are solved.
The project code looks reasonable - it appears to only fail because it is using old, out of date libraries. This should be an easy fix for someone who is familiar with the code, and able to perform tests.
Is it possible for someone to upgrade the axelor-docker files, so that the images can be built, as described in the instructions?
Hi Siddique, thank you so much! This is great work!
I built it, and it runs. The only issue I encountered was in
There is a double ‹ && › in lines 15-16. Once I took out the extra &&, it built cleanly. You might want to make that change in your fork.
I ran aio-erp in a VM, and it worked as expected. Very nice! I am very glad to see this working with fresh code
I had a quick look at the application, and it looks very nice. I will need to add volumes, to test it out further, but it is good to see. Would you be able to push your changes to the main repository, and regenerate the aio-erp image in docker-hub so that our helm chart can pull down from the official source? That would be outstanding.
Well-done Siddique, and thank you again! We will definitely be progressing our evaluation of Axelor, thanks to your excellent assistance.