You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no good way to add extra add-ons that require additional python packages.
Add-ons in /bitnami/odoo/addons can persist and it can be utilized to install custom add-ons without modifying the base image.
And I can install python requirement to the running container using source /opt/bitnami/odoo/venv/bin/activate && pip3 install -r /requirements.txt
But the helm chart utilizes the venv at /opt/bitnami/odoo/venv/ this is not part of any volume claim, therefore re-sets on every container start-up.
What is the feature you are proposing to solve the problem?
A good-way to use the odoo helm chart with custom modules that require additional python packages.
I could Imagine having a separate virtual environment inside the odoo data volume claim that is linked to the /opt/bitnami/odoo/venv/ e.g.: /bitnami/odoo/venv that users can install extra pip packages in.
What alternatives have you considered?
Installing them every time at start-up using the initContainer.
Please correct me if there already is another way to achieve this? 🙏🏻
The text was updated successfully, but these errors were encountered:
tbscode
changed the title
Ability to extend python packages without custom image build
[bitnami/odoo] Ability to extend python packages without custom image build
May 12, 2024
Thank you so much for the feedback! I agree that the UX could be improved with, for example, allowing via values.yaml to introduce a set of python packages and have the chart render the init container that installs the plugin. I have my concerns on persisting the full packages section of the virtual environment as it could potentially break security upgrades. However, auto-generating the pip instal init container could be a good first step. Thoughts?
We use init containers in other charts, but we did not cover this use case. Could you try first creating an init container that covers the use case? Then, using that as a base, we could add improve the chart.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/odoo
What is the problem this feature will solve?
There is no good way to add extra add-ons that require additional python packages.
Add-ons in
/bitnami/odoo/addons
can persist and it can be utilized to install custom add-ons without modifying the base image.And I can install python requirement to the running container using
source /opt/bitnami/odoo/venv/bin/activate && pip3 install -r /requirements.txt
But the helm chart utilizes the venv at
/opt/bitnami/odoo/venv/
this is not part of any volume claim, therefore re-sets on every container start-up.What is the feature you are proposing to solve the problem?
A good-way to use the odoo helm chart with custom modules that require additional python packages.
I could Imagine having a separate virtual environment inside the odoo data volume claim that is linked to the
/opt/bitnami/odoo/venv/
e.g.:/bitnami/odoo/venv
that users can install extra pip packages in.What alternatives have you considered?
Installing them every time at start-up using the
initContainer
.The text was updated successfully, but these errors were encountered: