From 047f4b72cb152f5d49dabdad596d43711d9af7e3 Mon Sep 17 00:00:00 2001 From: Brett Stoddard Date: Thu, 25 Feb 2021 16:01:07 -0800 Subject: [PATCH 01/11] fix name issue with build_moveit.bash --- build_with_moveit.bash => build_moveit.bash | 0 install_dependencies.bash | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename build_with_moveit.bash => build_moveit.bash (100%) mode change 100644 => 100755 install_dependencies.bash diff --git a/build_with_moveit.bash b/build_moveit.bash similarity index 100% rename from build_with_moveit.bash rename to build_moveit.bash diff --git a/install_dependencies.bash b/install_dependencies.bash old mode 100644 new mode 100755 From 785f50976de984549aae70629905a580a92c60bb Mon Sep 17 00:00:00 2001 From: Brett Stoddard Date: Thu, 25 Feb 2021 16:02:26 -0800 Subject: [PATCH 02/11] update readme for file name change --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 46f17a5..ef379e6 100644 --- a/README.md +++ b/README.md @@ -51,15 +51,15 @@ Or install manually by following the instructions below: - Give permissions to execute the bash script - ```chmod +x build_with_moveit.bash .``` + ```chmod +x build_moveit.bash .``` - If you have an Nvidia graphics card, run: - ``` ./build_with_moveit.bash .``` + ``` ./build_moveit.bash .``` Otherwise run - ```./build_with_moveit.bash -w .``` + ```./build_moveit.bash -w .``` 6. Drop into a Docker container the newly built image: From a00aab2f3e437dcec8004df1abaed86ed2695679 Mon Sep 17 00:00:00 2001 From: stoddabr Date: Fri, 26 Feb 2021 13:22:11 -0800 Subject: [PATCH 03/11] Update readme with issue fix add a common issue fix for a nvidia docker error --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 6d81d3c..c6eccb1 100644 --- a/README.md +++ b/README.md @@ -173,4 +173,10 @@ The `run_custom.bash` in this repository mounts the entire `uuv_ws` catkin works Common Issues --- +- If a NVIDIA graphics card isn't set up properly, running `./run_custom.bash dave_nvidia:latest` will result in something similar to the error below. This can be resolved by fixing the issue that is preventing the graphics card from being seen by your OS (for example, on a dual boot machine a power saving program running on windows may disable the graphics to save power requiring you to switch to windows and stop it) +```bash +docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.g\n0:459: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization\nerror: driver error: failed to process request: unknown.\ncharisma charisma- ROG-Zephyrus-G15-GA5030R-GA5030R: -uuy ws/src/daye/dockers | +``` + + From d96dca4a3f2db427e381541b1888874905d4cc31 Mon Sep 17 00:00:00 2001 From: stoddabr Date: Fri, 26 Feb 2021 13:26:04 -0800 Subject: [PATCH 04/11] add more info about problem making it more replicable --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c6eccb1..4b357ff 100644 --- a/README.md +++ b/README.md @@ -173,7 +173,7 @@ The `run_custom.bash` in this repository mounts the entire `uuv_ws` catkin works Common Issues --- -- If a NVIDIA graphics card isn't set up properly, running `./run_custom.bash dave_nvidia:latest` will result in something similar to the error below. This can be resolved by fixing the issue that is preventing the graphics card from being seen by your OS (for example, on a dual boot machine a power saving program running on windows may disable the graphics to save power requiring you to switch to windows and stop it) +- If a NVIDIA graphics card isn't set up properly, running `./run_custom.bash dave_nvidia:latest` will result in something similar to the error below. This can be resolved by fixing the issue that is preventing the graphics card from being seen by your OS (for example, on a dual boot machine a power saving program running on windows may disable the graphics to save power requiring you to switch to windows and stop it). To check if the NVIDIA card is setup properly, run `lspci -v | grep VGA` which should list your graphics card (if it doesn't then you may have a similar issue -- if it does tryp updating your drivers) ```bash docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.g\n0:459: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization\nerror: driver error: failed to process request: unknown.\ncharisma charisma- ROG-Zephyrus-G15-GA5030R-GA5030R: -uuy ws/src/daye/dockers | ``` From f0791641f21f8eadb37b2e7807df0fc4eb88e07a Mon Sep 17 00:00:00 2001 From: stoddabr Date: Fri, 26 Feb 2021 14:09:05 -0800 Subject: [PATCH 05/11] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4b357ff..e8402d1 100644 --- a/README.md +++ b/README.md @@ -173,7 +173,8 @@ The `run_custom.bash` in this repository mounts the entire `uuv_ws` catkin works Common Issues --- -- If a NVIDIA graphics card isn't set up properly, running `./run_custom.bash dave_nvidia:latest` will result in something similar to the error below. This can be resolved by fixing the issue that is preventing the graphics card from being seen by your OS (for example, on a dual boot machine a power saving program running on windows may disable the graphics to save power requiring you to switch to windows and stop it). To check if the NVIDIA card is setup properly, run `lspci -v | grep VGA` which should list your graphics card (if it doesn't then you may have a similar issue -- if it does tryp updating your drivers) + +- If a NVIDIA graphics card isn't set up properly, running `./run_custom.bash dave_nvidia:latest` will result in something similar to the error below. This can be resolved by updating your drivers ([how to install nvidia proprietary drivers](https://www.cyberciti.biz/faq/ubuntu-linux-install-nvidia-driver-latest-proprietary-driver/)) fixing the issue that is preventing the graphics card from being seen by your OS (for example, on a dual boot machine a power saving program running on windows may disable the graphics to save power requiring you to switch to windows and stop it). To check if the NVIDIA card is setup properly, run `lspci -v | grep VGA` which should list your graphics card (if it doesn't then you may have a similar issue -- if it does tryp updating your drivers) ```bash docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.g\n0:459: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization\nerror: driver error: failed to process request: unknown.\ncharisma charisma- ROG-Zephyrus-G15-GA5030R-GA5030R: -uuy ws/src/daye/dockers | ``` From 767f2d0e953923683b30a208e0adc2ad7eb244ef Mon Sep 17 00:00:00 2001 From: stoddabr Date: Fri, 26 Feb 2021 14:22:16 -0800 Subject: [PATCH 06/11] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e8402d1..6b21930 100644 --- a/README.md +++ b/README.md @@ -174,7 +174,7 @@ Common Issues --- -- If a NVIDIA graphics card isn't set up properly, running `./run_custom.bash dave_nvidia:latest` will result in something similar to the error below. This can be resolved by updating your drivers ([how to install nvidia proprietary drivers](https://www.cyberciti.biz/faq/ubuntu-linux-install-nvidia-driver-latest-proprietary-driver/)) fixing the issue that is preventing the graphics card from being seen by your OS (for example, on a dual boot machine a power saving program running on windows may disable the graphics to save power requiring you to switch to windows and stop it). To check if the NVIDIA card is setup properly, run `lspci -v | grep VGA` which should list your graphics card (if it doesn't then you may have a similar issue -- if it does tryp updating your drivers) +- If a NVIDIA graphics card isn't set up properly, running `./run_custom.bash dave_nvidia:latest` will result in something similar to the error below. This can be resolved by updating your drivers ([how to install nvidia proprietary drivers](https://www.cyberciti.biz/faq/ubuntu-linux-install-nvidia-driver-latest-proprietary-driver/) or [how to install nvidia docker tools](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html#docker)) (note: [nvidia drivers may break things](https://askubuntu.com/questions/882385/dev-sda1-clean-this-message-appears-after-i-startup-my-laptop-then-it-w)) fixing the issue that is preventing the graphics card from being seen by your OS (for example, on a dual boot machine a power saving program running on windows may disable the graphics to save power requiring you to switch to windows and stop it). To check if the NVIDIA card is setup properly, run `lspci -v | grep VGA` which should list your graphics card (if it doesn't then you may have a similar issue -- if it does tryp updating your drivers) ```bash docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.g\n0:459: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization\nerror: driver error: failed to process request: unknown.\ncharisma charisma- ROG-Zephyrus-G15-GA5030R-GA5030R: -uuy ws/src/daye/dockers | ``` From 62bef3bf4c2246df4d36bc63a8d80d47bcfbf428 Mon Sep 17 00:00:00 2001 From: stoddabr Date: Sun, 28 Feb 2021 19:41:41 -0800 Subject: [PATCH 07/11] Rename install_moveit.bash to install_with_moveit.bash --- install_moveit.bash => install_with_moveit.bash | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename install_moveit.bash => install_with_moveit.bash (100%) diff --git a/install_moveit.bash b/install_with_moveit.bash similarity index 100% rename from install_moveit.bash rename to install_with_moveit.bash From 942b0b5769eeadc65ce64cc3a6577f8be9e9bfaf Mon Sep 17 00:00:00 2001 From: stoddabr Date: Sun, 28 Feb 2021 19:43:54 -0800 Subject: [PATCH 08/11] revert readme build_moveit to build_with_moveit --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 6b21930..6ba6b96 100644 --- a/README.md +++ b/README.md @@ -51,15 +51,15 @@ Or install manually by following the instructions below: - Give permissions to execute the bash script - ```chmod +x build_moveit.bash .``` + ```chmod +x build_witb_moveit.bash .``` - If you have an Nvidia graphics card, run: - ``` ./build_moveit.bash .``` + ``` sudo ./build_with_moveit.bash .``` Otherwise run - ```./build_moveit.bash -w .``` + ```./build_with_moveit.bash -w .``` 6. Drop into a Docker container the newly built image: From 03a19e3a7f398398813d0316214ff8d7f4241473 Mon Sep 17 00:00:00 2001 From: stoddabr Date: Sun, 28 Feb 2021 19:44:12 -0800 Subject: [PATCH 09/11] Rename install_with_moveit.bash to install_moveit.bash --- install_with_moveit.bash => install_moveit.bash | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename install_with_moveit.bash => install_moveit.bash (100%) diff --git a/install_with_moveit.bash b/install_moveit.bash similarity index 100% rename from install_with_moveit.bash rename to install_moveit.bash From 08b1505126895af9560121b78d07a6a04761d559 Mon Sep 17 00:00:00 2001 From: stoddabr Date: Sun, 28 Feb 2021 19:44:32 -0800 Subject: [PATCH 10/11] Rename build_moveit.bash to build_with_moveit.bash --- build_moveit.bash => build_with_moveit.bash | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename build_moveit.bash => build_with_moveit.bash (100%) diff --git a/build_moveit.bash b/build_with_moveit.bash similarity index 100% rename from build_moveit.bash rename to build_with_moveit.bash From 25fd53f58e982cbd02e57c76c975c8c5e56d4909 Mon Sep 17 00:00:00 2001 From: stoddabr Date: Sun, 28 Feb 2021 20:18:56 -0800 Subject: [PATCH 11/11] add note about sudo to common issues --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6ba6b96..b8fb85e 100644 --- a/README.md +++ b/README.md @@ -172,7 +172,7 @@ The `run_custom.bash` in this repository mounts the entire `uuv_ws` catkin works Common Issues --- - +- If a permission denied error occurs, try running with `sudo ` followed by the command - If a NVIDIA graphics card isn't set up properly, running `./run_custom.bash dave_nvidia:latest` will result in something similar to the error below. This can be resolved by updating your drivers ([how to install nvidia proprietary drivers](https://www.cyberciti.biz/faq/ubuntu-linux-install-nvidia-driver-latest-proprietary-driver/) or [how to install nvidia docker tools](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html#docker)) (note: [nvidia drivers may break things](https://askubuntu.com/questions/882385/dev-sda1-clean-this-message-appears-after-i-startup-my-laptop-then-it-w)) fixing the issue that is preventing the graphics card from being seen by your OS (for example, on a dual boot machine a power saving program running on windows may disable the graphics to save power requiring you to switch to windows and stop it). To check if the NVIDIA card is setup properly, run `lspci -v | grep VGA` which should list your graphics card (if it doesn't then you may have a similar issue -- if it does tryp updating your drivers) ```bash