Docker image for Jasper available

[Daniel Chalef]

Hi all

I've created an armhf (Raspberry Pi 2) Docker image for Jasper. If you're interesting in trying out Jasper, and somewhat daunted by the installation process then a docker image is a good way to go. Likewise if you're developing for Jasper.

You can pull the image with the following Docker command:

$ docker pull danielchalef/armhf-jasper-docker

Please see the github project for detailed instructions on how to use the image, and the Dockerfile (should you want to build the image yourself):
https://github.com/danielchalef/jasper-docker

Hope it's helpful.

Daniel

[Matthew Curry]

Any instructions on starting it? ports/etc?  Can you give me an example of using it?

[Gnaush]

I just started trying this out myself with Daniel's docker image.

I downloaded an SD card image for the Pi from here: http://blog.hypriot.com/downloads/

and then wrote the image to the microSD card and booted the Pi.

Then I upgraded docker from the newest .deb download available from the same hypriot blog page.

Then I started following the instructions on Daniel's page: https://github.com/danielchalef/jasper-docker

That's as far as I got...

I started reading this page: https://github.com/jasperproject/jasper-client/issues/364 with discusses installing Sphinx5pre alpha

It references this as well, which is quite detailed: https://wolfpaulus.com/jounal/embedded/raspberrypi2-sr/

[Daniel Chalef]

Yes, detailed instructions can be found on Github.

I did not have much success with Sphinx. Compared to Google STT, Sphinx was
slower (higher latency) and had a lower recognition rate. Granted, having
the STT running on the device may be preferable to some. I did try get
Julius working but the lack of a language model was a little daunting:
http://julius.osdn.jp/en_index.php

Please do fork my project and give the other STT engines a go. Alternatively,
use my docker image as an upstream in your own Dockerfile:

FROM danielchalef/armhf-jasper-docker:latest

[Daniel Chalef]

Matthew, while you can certainly just RUN the docker image as is, it is designed to be used as an upstream image that you build on. 

So for example, you can create your own Dockerfile and use my image as an upstream, with your own customization / additions built on top.  When running the image as a service, the final instruction in your downstream Dockerfile would be a CMD that would start the service. 

Why use docker? I found it super convenient when developing on top of the Jasper framework. It allows:

• It provides a stable base, compartmentalized container for you to develop and run on. No more messing up your Pi installation when installing conflicting dependencies etc. No more wondering why something no longer works following an apt-get update.
• Easily pull images on to multiple Pi devices. No more lengthy writing to and juggling of SD cards.
• Compilation on faster 3rd-party ARM hosting services, significantly speeding up your development cycle. Scaleway offers incredibly cheap bare-metal armv7 servers with 2GB of RAM, and SDD storage. Install docker on to the cloud server. Install git. Pull from your Github repo. Build. Develop / modify. Build. Iterate. And then pull the image from Dockerhub on to your Pi, and test.

[Daniel Chalef]

Matthew, I noticed from other posts that you've struggled to get Jasper working on the AMD64 platform (i.e. Intel/AMD 64 bit Linux). I've quickly hacked together an AMD64 Dockerfile for you to use. I haven't tested it extensively, and have not pushed an image to Docker Hub.

To get started:

$ git clone https://github.com/danielchalef/jasper-docker.git 
$ cd jasper-docker
$ docker build -t "jasper-amd64-dev" -f Dockerfile.amd64 .

And then follow the rest of the instructions on Github. Note that the label of the image has changed (highlighted above).

Let me know if you have difficulty getting it working.