Related!
I have just tried this with success after a lot of wrangling. The images haven’t been updated in a couple of month so the latest version is still version 7 in beta, but I was able to make it work with each service in a different container (with the multi-container images based on alpine).
I’m having a problem to update the image right now because bench update --ugrade
expects to have access to the redis-server which isn’t the case in a multi-container setup.
I got around the bench update --upgrade
redis error by emptying the /home/frappe/bench-repo/bench/patches/patches.txt
file for now.
We are going to start to build some containers for this in our hosted environment. It will be on openshift origin so when it is done i will share the repos with you guys. They will be a centos base. I am also thinking of using this too GitHub - africlouds/erpaas
I crafted the erpaas app quickly as I was discovering and learning ERPNext a few weeks ago, so it is not complete and definitely not tested and not production readyh. It is currently running the site https://intego.rw (also not for production so far) with GitHub - africlouds/intego_rw . I hope it will get better with time
@RWEMA_Aimable thx i’ve tried to install on last V7 development version and getting error while openings erpnext service page…also not displaying the app on desk
@RWEMA_Aimable well anyway thanks for making it and I hope I can help to make it better. You have some nice extensions that you have started…
any plans to separate any of the multiple services building ERPNext?
As far as I could follow this is not possible entirely (due to how ERPNext is glued together as I understand)
But for example separating | MariaDB | nginx | all the rest | … might be a start.
I think that the biggest issue is that you only provide one way to install bench with your setup script.
I’m not a big fan of this way as I like to know what I install and why.
Maybe, if you provide some manual setup instructions:
- install mariadb
- install reddis
- install Python dependencies (in a virtualenv)
- install bench (still in a virtualenv)
- add some settings to hit mariadb and reddis
- start using it
I didn’t dig at all in your code base so I’m not aware if it’s possible or not. But I’m clearly not trying to install it as it’s require superusers privileges, but using Mac OS with homebrew, I almost never have to use sudo to install anything.
I know that this thread is about Docker for ERPNext, but IMHO bench is a pain to install and that’s the entrypoint to start using and building with ERPNext.
Howdy All. Our company recently discovered ERPNext and is evaluating it for use in house. We have our entire infrastructure built around Docker and Amazon ECS. My first tasks are to make ERPNext work in a Docker environment before we can use it.
I have taken a look at the following public Docker hub images:
https://hub.docker.com/r/davidgu/erpnext/
https://hub.docker.com/r/raman/erpnext/
https://hub.docker.com/r/donysukardi/erpnext/
The first two essentially treat the container as if it were a VM. donysukardi’s repo started an attempt to separate the components into individual containers. My preference is for the latter, so I’ve taken that as my starting point and submit a PR to donysukardi. He may not be maintaining his repo any longer though.
That said, I’ve got an experimental build working with ERPNext running on 11 docker containers. I’m very, very new to ERPNext–so I may be missing something–but it seems like it is working well.
I was hoping the community could help me validate it and continue the work.
Here is my fork:
Anyone with a Docker install should be able to get this running in a couple minutes. If you have some time please take a look and give it a shot.
Right now all the secrets are hard coded, so that needs to be changed ASAP.
What do you all think otherwise?
Thanks for all the previous work, both with ERPNext on Docker and ERPNext in general.
Right now all the secrets are hard coded, so that needs to be changed ASAP
If I recall previous comments in regards to this correctly this isn’t something which the core team has on it’s list of priorities but would be open to accept PR’s about
In that case I think for this container image what I’d do is have the startup script handle writing the site_config.json
based on ENV vars. Then no modification would be needed in Frappe.
Of course it would be way better if Frappe read directly from ENV vars rather than config files. So +1 for that still.
Thanks!
@ianneub just clarifying … testing should be done using your docker-compose branch, not ‘master’, correct?
EDIT git clone --branch docker-compose GitHub - ianneub/docker-frappe: Dockerized image of Frappe
That is correct.
IMAGE_NAME=donysukardi/frappe:stable ./hooks/build . is failing with the following errors on Ubuntu 16.04 and docker-compose version 1.7.0 and Docker version 1.11.0
Any hint?
/usr/include/python2.7 -c psutil/_psutil_linux.c -o build/temp.linux-x86_64-2.7/psutil/_psutil_linux.o
psutil/_psutil_linux.c:19:27: fatal error: linux/version.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1
----------------------------------------
Command "/usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-7_dXAL/psutil/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-8n2pXk-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-7_dXAL/psutil/
The command '/bin/sh -c git clone -b $BENCH_BRANCH --depth 1 https://github.com/$FRAPPE_USER/bench bench-repo && sudo pip install -e /home/$FRAPPE_USER/bench-repo --no-cache-dir && mkdir -p frappe-bench && cd frappe-bench && mkdir -p apps logs sites/localhost config && bench setup env && sudo bench setup sudoers $FRAPPE_USER && bench setup socketio && bench get-app frappe https://github.com/frappe/frappe --branch $FRAPPE_BRANCH' returned a non-zero code: 1
You could try AthenaPDF
https://github.com/arachnys/athenapdf
as drop in replacement for wkhtmltopdf, its already powered by docker and you will avoid lots of crazy problems that will be caused by wkhtmltopdf. just a suggestion
Same error on develop branch