Mycroft Community Forum

Mycroft and Docker images, a different approach

General Discussion
#1

Hi community,

During the past few weeks I worked on building Docker images for Mycroft using a different approach, the micro-services one.

Basically each Mycroft services such as audio, skills, etc… will run into their own container with their own /shared volumes (when required).

The main differences with the official Mycroft images are:

  • Micro-service approach
  • No more skills “re-installation”
  • Automatic nightly build (dev only, until backports are applied to master) and pushed on Docker Hub
  • Multiple CPU architectures support
  • docker-compose support
  • GPIO support for Raspberry Pi
  • A container dedicated to the command line

It’s not perfect for sure but it fits my needs/requirements for the project I’m working on. Fill free to share your feedback and to contribute. :partying_face:

3 Likes
#2

That looks awesome, looks like you’ve put a ton of work into it, and there are so many improvements on the current image.

1 Like
#3

Amazing! Am going to play around with that immediately!

2 Likes
#4

Yeah I had some fun evenings and I gained few more white hairs :rofl: I really enjoyed the learning of the buildx feature which allows the multi-arch support but overall I still be a Podman fan boy ^^

@mdverhoeven that would be great, I mostly tested the containers on ARM 64-bit so some surprises could happen! :crazy_face:

1 Like
#5

Do you have any feedback to share, any bugs?
The PulseAudio part could be a bit tricky. :upside_down_face: