-
Notifications
You must be signed in to change notification settings - Fork 271
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
./run_demo.bash: I meet some problems and solutions. #49
Comments
Follow up to osrf/car_demo#49
It's highly not recommended to run docker as sudo. As per the readme make sure that you have added your user to the docker group. Then you should be able to run docker without sudo. If you're running as sudo the --user option is not useful as 'root' already exists inside the container. I've pushed a change to make it more robust: osrf/rocker@a845001 But you should figure out what your permissions issue is before trying to continue. Note that if you've run things are root before there may be files that you need to clean up the permissions on. But the instructions shouldn't be changed to recommend sudo. |
thx brother @tfoote , I get it! I didn't find the rocker about the explanation of |
When I execute these steps before |
@JKTesla It looks like |
So brother @tfoote @sloretz , the run_demo.bash need get some corresponding changes? I just find tips here , I also need remove the docker-py python module from my system?Because my simulator can not work sometimes……report the wrong log as follows: |
@JKTesla I am facing the same problem, how do you pass it ?? |
@JKTesla Please copy and paste and use block quotes instead of screenshots so that content can be searched as well as copy and pasted. You may need a slightly newer version of docker-py than is on your system. I've opened a ticket at osrf/rocker#16 to get a better error message |
Sorry for screenshots. I have already installed docker before.And use this instruction.And my docker version as follows:
As your advice, I installed the docker-py, using pip install docker . But the previous problem still exists..
|
This modification works, Thx.
As @tfoote advice, I have upgraded docker-py in my system
And I once installed Python3.7 in my system(Ubuntu14.04), reset Python2.7 (default in Ubuntu14.04) to the highest priority(hope to keep the version consistent,both python and docker-py)
Is it because of the Chinese Internet firewall?make me create docker_client unsuccessfully? |
btw, in the future, if I can set rocker at local computer by replacing below command: |
You need to be careful about into what python environment you are installing tools. rocker is a python3 only package. Any python2 package you install will not effect it. Your pip installs are going into python2.7 directories so are not accessible.You need to use pip3 or some other equivalent method to get the modules into your python3 path. |
I think this will be fixed when osrf/rocker#18 is merged. |
Hey buddy @kimchicanh , the rocker's problem had been solved by contributors, I can run demo Successfully. Maybe you can also have a try. |
I keep doing using our simulator to do somethings interesting.
when I
./run_demo.bash
, The log told mePermissionError: [Errno 13] permission denied: ...
as follows:So I just to
sudo ./run_demo.bash
, but the log told meuseradd: user 'root' already exists Cannot run if build has not passed.
as follows(in the bottom line):I have no idea about it. So find The user ‘root’ already exists.
So I decide to remove
--user
in therocker --nvidia --user --exec --devices /dev/input/js0 /dev/input/js1 -- osrf/car_demo
.This time, I
sudo ./run_demo.bash
again, usingrocker --nvidia --exec --devices /dev/input/js0 /dev/input/js1 -- osrf/car_demo
.The simulator can run well again.So @tfoote, I think whether we can remove
--user
thoroughly and usingsudo ./run_demo.bash
?The text was updated successfully, but these errors were encountered: