Hi folks!
I know a bunch of you wanted to get access to the Docker slides after the talk. You can find that here:
I've got a busy day today, but I'll come back later in the evening for some helpful links to get started with Docker.
ROS is kind of a hack when it comes to environment sandboxing because it essentially works by monkey-patching your bash environment. Virtual environments are kind of a hack when it comes it environment sandboxing because it essentially works by monkey-patching your bash environment. What are we using? Both.
This script will generate a Python 3.6 virtual environment called venv-ros-solo
in the directory that the
script is located. Note that means that you need to have python3.6-venv
installed. On Debian/Ubuntu
variants, this should be pretty easily doable with sudo apt install python3.6-venv
.
If you want to work on gym_solo
, or use any version of the repos that isn't master
, you need to replace those repos
in the docker container via a volume mount.
Assuming your filestructure is as follows and your docker image is named solo8:sb-gpu
, you can just ./run.sh
and it
should start JupyterLab within the container.
Required filesystem:
I constantly find myself rewriting these instructions over and over again, so I figured that I'll write 'em once and reference this document when needed.
- There is a file in the root directory named
requirements.txt
. This file should be hold all of the packages required for the project. This file can be generated by runningpip freeze > requirements.txt
on UNIX based systems. - That the project is using Python 3. Most of my projects are written in Python 3, so this condition will usually be true. If this not the case, it will be explictly written as such in the
README.md
. The only major change to use Python 2 is to replacepython=3
withpython=2
when the step comes.
If you already have pip installed (Just try running pip
from the command line), simply
Connecting to WPI network with wpa_supplicant or wicd (or other) | |
Download client both certificates (CA and the .p12 from WPI-Wireless-setup) Make sure to download the CA cert in pem format. It may work in the default format, but I can not confirm that. | |
Make sure to save both certs and everything created in this tutorial in a useful directory, such as /usr/share/wpiwificerts | |
All commands should be run in that same directory, some commands may need to be run as root | |
Create client certificate | |
openssl pkcs12 -in certificate.p12 -out cert.pem -clcerts -nokeys | |
(enter @wpi.edu) password when prompted |