-
Hi there, I'm trying to commit to a fork of Inventree, from a docker dev setup on a debian VM. Installation ok, and dev server running. Git works fine, authentication ok, commit ok, etc. Then I've ran : it seems working fine then i made some modification to a file and run
and I can see all tests and their result (all ok for the next steps) but then when i of course I haven't any python package installed, every thing is packed in containers, so no venv. My googling do not lead me to any sort of clues, and as you can imagine i'm a deep newbie on that process. What Have I missed? Should I consider going for a baremetal install? or just install pyhton package and commit on a specific way ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
You get this error outside of the docker container where Python and everything is installed. While you did the setup dev thing, you installed the git hook pre commit, which expects to be run in an virtual env which lives in the container. But as you are outside of the container, you have not activated this venv (you even don't have python there, which is totally fine). For fixing this, you can commit with the |
Beta Was this translation helpful? Give feedback.
You get this error outside of the docker container where Python and everything is installed. While you did the setup dev thing, you installed the git hook pre commit, which expects to be run in an virtual env which lives in the container. But as you are outside of the container, you have not activated this venv (you even don't have python there, which is totally fine). For fixing this, you can commit with the
--no-verify
flag outside of the container, or exec into it, and run the commit there. As you already run the tests, you don't have to worry, that the precomit will find something.