Univention Bugzilla – Bug 52150
install kelvin and its deps directly into container, don't use virtualenv
Last modified: 2021-02-23 09:29:48 CET
The use of a Python virtualenv in the Kelvin Docker container is not required. There is no need to create a separate Python installation inside the Docker container, as there will never be another. The use of a virtualenv however complicates the build and the usage (and slightly raises the image size). For example is it always necessary to active the virtualenv before using scripts and the ucr cli. Install the Kelvin API and its dependencies directly into the Docker container. Such a change has already been done for the ucsschool-id-connector, and there were no negative side effects, only positive.
Fixed in: [feature/kelvin 8291b5a1c] Bug #52150: build Docker image without virtualenv
Code Review: OK Copyright updates: OK REOPEN for build and new Kelvin App version for final tests.
A new Docker image was build and the Kelvin app version 1.3.0 can now be installed form the test appcenter.
Final QA → All OK → VERIFY - Kelvin app version 1.3.0 was uploaded to test appcenter. - Changelog OK - venv is no longer in Docker container - tests run with `python3 -m pytest`
A Kelvin API app with the changes in this bug has been published.