Public | Automated Build

Last pushed: a year ago
Short Description
Short description is empty for this repo.
Full Description

OpenCog's Docker library

This repository is used for setting different docker containers for the various
components/dependencies/tools/repositories/configurations associated with the
OpenCog project. The dockerfiles here are designed to be built in an additive way.

1. Dockerfiles for Robot Operating System (ROS)

Dockerfiles for demoing and working with various different robot heads
and bodies, mostly those from Hanson Robotics. Several of the heads are
modeled with blender, and so can be usefully worked with and controlled
even without a physical robot.

Currently, the most sophisticated demo here is that of Eva, a female
head created by Hanson Robotics. She can track human faces visible to
her (via webcam), interact by displaying a variety of emotions and
facial gestures, and perform lip sync for speech. The Eva blender file
allows all this without the need of a physical robot head to be

Docker is used primarily because there are a large number of software
dependencies that must be installed in order to make this all work.
This includes the Robot Operating System (ROS), Blender, Pololu motor
drivers, a variety of ROS webcam and face-tracking/saliency nodes,
OpenCog, and other add-ons.

Docker image structure:



Images available at

Pull using, e.g., docker pull ros-indigo-opencog

Organizational Notes:

The base and blender images should be general enough to allow various
different robots to be brought up and demoed.

  • ros-indigo-base provides a base set of ROS packages, nothing more.
    The packages are sufficient for performing ROS demos, but no actual

  • ros-indigo-blender adds blender to the base, thus allowing ROS nodes
    to control blender animations.

  • eva provides the full Hanson Robotics Eva head demonstration. This
    includes vision and sound processing, motor controls, scripted
    behaviors, and a web user interface. See the README in indigo/eva
    for more details.

  • ros-indigo-dev provides additional development packages, allowing
    developers to build and test inside of docker containers. XXX
    this needs to be cleaned up and replaced by one of the above!?

2. Dockerfiles for OpenCog

The following are details about dockerfiles found in opencog and buildbot
directories. On how to use read opencog's README.MD and

The Dockerfiles in the directories opencog/tools/distcc, opencog/embodiment and opencog/cogserver are not detailed because they are not in active use.

Docker image structure:

  ├─buildbot_* (Where * = atomspace, cogutils, opencog, moses)
    ├─opencog/opencog-dev:cli (for a dev environment)


Organizational Notes:

  • opencog/opencog-deps:utopic: ubuntu 14.10 based image with all OpenCog's
    dependencies installed.

  • opencog/opencog-deps:latest: ubuntu 14.04 based image with all OpenCog's
    dependencies installed. This forms the base of opencog/cogutils. It
    likely will be updated to the latest LTS as it is released. Has some command
    line tools for use by developers.

  • buildbot_*: Is used for buildbot found here

  • opencog/cogutils: It is the base image for opencog/opencog-dev:cli,
    opencog/opencog-dev:ide and opencog/moses images. It installs cogutils
    over opencog/opencog-deps image. The main reason for having this is to
    speed up rebuilds as one doesn't ave to rebuild the opencog-deps image,
    unless there are dependency changes, and rebuilding this image will suffice
    for updating the dependent images.

  • opencog/opencog-dev:cli: Mainly for running/developing through a shared
    filesystem between host and container.

  • opencog/opencog-dev:ide: To be used for developing using ides. QtCreator
    is installed.

  • opencog/moses: It has moses and R installed. R is installed for those
    who want to use the R binding for moses. The binding is not yet included but can be found here.

  • opencog/relex: It is a self-contianed image for running relex and
    linkg-grammar servers.

3. Usage

  • To run the demos and other containers, docker must be installed. Instructions
    can be found here. The Giving non-root access
    section on the page explains how to avoid having to use sudo all the time.

  • The file in opencog directory is used for building some of the
    images. Run ./ -h for viewing available options.

  • To use docker-compose follow the instruction in the README file in the
    opencog directory.

Docker Pull Command
Source Repository

Comments (0)