New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RASA X error on model train when volume mounted in docker image #8598
Comments
yes I also have that one but that is a consequence of not being able to execute the previous operation I believe. If I assign the models folder the permission 1001:0 it works but this should not be an option I started the container with the user owner of the folder in the host FS. |
This could be the reason: rename(2): OverlayFS does not fully support the rename(2) system call. Your application needs to detect its failure and fall back to a “copy and unlink” strategy. The container is using overlay and the operation is issuing a rename operation, can you change it to a copy and unlink? |
@tczekajlo do you have an idea what this might be caused by? |
It's right that the
@gioppoluca You mentioned that you bind mount the app folder, but it looks like You can check it by executing e.g. the Please be sure that |
I'm closing it because of the lack of further updates. |
Any updates regarding this |
Rasa version: 2.3.1
Rasa SDK version (if used & relevant): not relevant
Rasa X version (if used & relevant): 0.39.0
Python version: The one in the official docker image
Operating system (windows, osx, ...): CentOS 7 (Official Docker image)
Issue:
I' m using the official docker images to run a custom docker compose file and I bind mount the app folder.
The container runs with a user 1000:1000 that is needed since in the host there is not the user and the group 1001.
The container and rasa x runs correctly BUT when I try to train the model it breaks due to the fact that the "move" from the TMP cannot be done since the file systems are "not the same" since the app folder is a volume of the container.
BTW when the rasa-X image start it only create the user in passwd, BUT NOT the group so there is also the problem of the group not being known and also this could cause troubles?
Error (including full traceback):
Command or request that led to error:
probably the internal command that wants to mode the model from the TMP to the MODAL folder, but I have a host binded volume and docker raises an error
Content of configuration file (config.yml) (if relevant):
not relevant
Content of domain file (domain.yml) (if relevant):
not relevant
The text was updated successfully, but these errors were encountered: