Closed ruffsl closed 4 years ago
What is your ROS_DISTRO?
What is your ROS_DISTRO?
Dashing, as in the Dockerfile:
Is your rosdep database up to date? Or did rosdep update
rely on the docker cache?
Looks like the key is valid and was added a couple weeks back: https://github.com/ros/rosdistro/blob/master/rosdep/python.yaml
https://github.com/ros/rosdistro/pull/22263
python3-docker was added in this PR https://github.com/ros/rosdistro/pull/22263/files - my guess is this is a Dockerfile caching problem from rosdep update
being run separate from rosdep install
, similar to how Dockerfiles should run apt-get update && apt-get install
to prevent discrepancy.
EDIT: @mikaelarguedas yeah I think you're right about the docker cache https://github.com/ros-swg/turtlebot3_demo/blob/master/Dockerfile#L5
Shoot, I rebuilt the entire ros stack, but the make file in the osrf/docker_images tags the image using the full tag, while the Dockerfile here uses the abbreviated tag. That short form is something that the DockerHub post push hook adds. I summary, when building from scratch, don't forget to tweek the Dockerfile FROM directive or retag the new image locally:
docker tag osrf/ros:dashing-desktop-bionic osrf/ros:dashing-desktop
It looks like the
launch_ros_sandbox
package is declaring a dependency that rosdep can not resolve. Could amazon please fix this either with adding the dependency to rosdistro repo, or adjusting thelaunch_ros_sandbox
to avoid blocking the demo's docker build?cc @piraka9011 @emersonknapp @thomas-moulard