- #DOCKER MAPPROXY HOW TO#
- #DOCKER MAPPROXY INSTALL#
- #DOCKER MAPPROXY UPDATE#
- #DOCKER MAPPROXY OFFLINE#
When I run the resulting container I see all the additions to the ENV that virtualenvwrapper makes (you can see all of them by executing the "set" command without any args), and the script to be sourced is there too. So I comment out the RUN lines and it builds without error.
Bash complains source needs an argument - the file to be sourced. The build fails on the line I try to source the virtualenvwrapper script.
#DOCKER MAPPROXY INSTALL#
Pip3 -disable-pip-version-check install -upgrade bts_tools RUN mkvirtualenv -p`which python3` bts_tools & \ # RUN mkdir /home/tester/.virtualenv & virtualenv -p`which python3` /home/bts_tools/.virtualenv/bts_tools # Create a virtualenv so uwsgi can find locale # installed, as bash complains "source needs a single parameter"ĮNV VIRTUALENVWRAPPER_PYTHON /usr/bin/python3ĮNV VIRTUALENVWRAPPER_VIRTUALENV /usr/bin/virtualenv # virtualenv? How do you "source" the script? Doesn't appear to be # Yes, but not always, such as with virtualenvwrapper. # After above, can we use those installed in rest of Dockerfile? Virtualenv virtualenvwrapper sudo nano & \ RUN apt-get install -y python3 python3-dev python3-pip \ # to insure they are the same as on host setup.
#DOCKER MAPPROXY UPDATE#
# Skipping apt-get update to save some build time. This is the Dockerfile I'm using: # Docker image definition for testing I have stripped away all my app specific additions to narrow down the problem. The command line functionality works, but when I make a request of the flask app uwsgi / python has a problem with locale: Fatal Python error: Py_Initialize: Unable to get the locale encoding and ImportError: No module named 'encodings The app has command line functionality and a separate flask web app, hence the need for uwsgi. In my first attempt I installed almost everything with apt-get, including uwsgi. I will eventually use docker-compose, but I wanted to start by getting my feet wet with it all in a single docker container. I am trying to build a docker image and am running into similar problems.įirst question was why use a virtual env in docker? The main reason in a nutshell is to minimize effort to migrate an existing and working approach into a docker container. So why is workon returning an error when the mapproxy virtualenv exists? The same error happens when I isolate that last line into a third Dockerfile building on the second. WORKON_HOME & PROJECT_HOME both exist (defined in the parent image) and point to the correct locations (and are used successfully by "mkproject mapproxy").
Workon is being called, but for some reason it can't find the mapproxy virtualenv. But when I try and build with the last line, it gives a workon error: ERROR: Environment 'mapproxy' does not exist. If I comment out the last line it builds successfully and I can spin up the container and run "workon mapproxy" manually, not a problem. However, the following Dockerfile (based of the first image, "base_image_14.04") falls down at the last line: FROM base_image_14.04 I am using the resulting image as a "base image" for further use. Project Motivationīuilt for competing in the University Rover Competition by Ryerson University's robot club.I have a Dockerfile that successfully creates a virtualenv using virtualenvwrapper (along with setting up a heap of "standard" settings/packages in our normal environment). In 2013 there was some discussion about Google's Terms & Conditions stating that you are only allowed to access the tiles through Google's API (ie.
#DOCKER MAPPROXY HOW TO#
How to publish GPS coordinates over ROS? rostopic pub /novatel/fix sensor_msgs/NavSatFix ""
#DOCKER MAPPROXY OFFLINE#
ROS Offline Google Maps for MapViz MapViz (Tile_Map plugin)