-
Notifications
You must be signed in to change notification settings - Fork 3
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
Segmentation Fault #4
Comments
Running the docker container with arguments causes a segmentation fault.
|
I created a fresh build and ran torcs inside a docker container, it is working fine. But when I try to copy/mount ur |
I was able to resolve the error by copying Hope this helps you update your repository and resolve this issue |
Hey, sorry for the slow reply. The seg fault is caused by torcs trying to access a file that does not exist. |
So before the volumes were mounted to the container based on the current working directory (with Because I am currently unable to test if everything works as intended I pushed on this branch Could you please check? |
Sure, i'll check it and get back to you |
Still get the same error the cofigs folder provided in your directory.
Running the container with the configs files I copied from your docker image work perfectly. |
Thanks for checking, this is weird though. You said that you run the container with the volumes
Are you sure that Another thing you could try is see where it is failing (just to be sure it's a missing config, but I am pretty certain that is the cause). Run torcs with the I am sorry but as of now I cannot properly support and help this issue, or update and cleanup this repository as I would want. |
Yes, its working fine for me after I copied the config folder from inside the docker image and replaced the configs folder present in your repository. |
Unable to start torcs after copying configurations file to correctly set up torcs for vision
The text was updated successfully, but these errors were encountered: