Thanks for your feedback too. Now I have 1 vote for and 1 vote against :-).
I don’t plan to use several docker-applications or docker on different RPi’s.
And you seem a lot more savvy then me, I don’t know what a podman is, dev time and all that kind of things :-).
Podman is on my to do, last time I tried the arm64 support was not great. I tried docker-rootless and felt a performance issue mostly related to the filesystem.
@Taxicletter the best way to know will be to try different things! Enjoy 
@Taxicletter, welcome to the community 
I had the same idea and wrote a “cookbook” on how to install mycroft and a music playing stack. You can download it from mycroft-tools/smartBoombox.pdf at master · mike99mac/mycroft-tools · GitHub
It describes installing Ubuntu server, but Raspberry Pi OS shouldn’t be much different.
It’s still very “alpha”, but if you use it, any feedback would be appreciated. Maybe I could add a section on installing Raspberry Pi OS as an alternative.
Thanks.
-Mike MThanks. I’ve installed Docker and now I’m installing Mycroft, which seems to take a long time (but everything is running, no worries).
I think everything went OK, but now I’m stuck. I’m using these instructions: Docker - Mycroft AI,
and I’m stuck on this part: “Running Mycroft for Docker”.
I don’t know where I should do this: " Just replace the directory_on_local_machine with the path you want the container mapped to on your local machine" and they don’t explain how to do this “Set PULSE_SERVER env variable” and “Share pulseaudio’s cookie”.
I tried copying the code underneath, but somehow it doesn’t copy and copying line per line gives an error in the first line, I need to set an argument…
I’ll try further, but meanwhile, if you have hints or tips 
-v directory_on_local_machine:/root/.mycroft
what reads create a volume (-v) mapping directory_on_local_machine to the one inside the container (/root/.mycroft)
the ones attributed with -e are environmental variable. ie
-e PULSE_SERVER=unix:${XDG_RUNTIME_DIR}/pulse/native is the one talked aout
this goes along with
-v ${XDG_RUNTIME_DIR}/pulse/native:${XDG_RUNTIME_DIR}/pulse/native
you have to check if there is something at ${XDG_RUNTIME_DIR}/pulse/native, resp. where it is to map it in.
The same would apply to the cookie.
But my understanding is you want to docker up smartgics (microservice) docker. They have a different structure. Those are the instuctions
That looks more complicated than I understand… Thought it would be an easier process. I really don’t understand “what reads create a volume (-v) mapping directory_on_local_machine to the one inside the container” Creating a volume?? Mapping??
I don’t know what smartgics or microservice are either, I didn’t think I was dockering anything up there.
I understand basic terminal commando’s and I can follow a manual, but since this manual seems to stop halfway through, I’m stuck as well :-).
The info on Network Setup – PulseAudio is way to complicated for me. They offer choices and I have to decide on info I don’t understand.
Is the way to install Mycroft WITHOUT docker as complicated as this?
(Thanks for your feedback, by the way, I forgot to mention that 
)
Since this is kind of a new topic, I made a new topic for it. (Running Mycroft for Docker)
forget about docker and install it using the usual method
That’s why i suggested that in the first place. You would have to dig through docker documentary otherwise to understand the syntax to be able to apply the specifics.
I’ll do that! I didn’t know using the docker was more complicated, I thought it would be easier somehow. Thanks!
Maybe one more question: how can I now uninstall all I installed? It was quite a lot, so it would be lost space.
BUT: this doesn’t spare you the work on the sound config since you’re using “Google AIY Voice HAT”. There are additional steps like here to perform.
I already got the speaker and mic working, but I see there’s more to it.
Thanks, I’ll bookmark your comment for later!
I usually just copy a fresh Linux image to the micro-SSD card, start from square 1 and update my notes along the way.
-Mike M
That’s a very clean and wise way to work I guess… I’ll try it that way next time
Oh, and I just remembered a “gotcha” - sometimes (usually?) networking is confused/slow/dropping connections when trying to build a new system on a previously used SSD card. Rebooting the home router/wifi has solved the problem. So after you re-flash the SSD, but before staring to rebuild it, a reboot of the router is recommended. My hunch is that the routing tables have values for the previous system, whereas the new system has the same macID, but different routing values, but I have no way of proving that. Hope this helps.
-Mike MThanks for the tip, but I don’t seem to have those network-troubles.
Hello! I’ve made a Unofficial Mycroft AI Raspberry Pi image builder on Github Actions. You can find the images here Releases · kleo/picroft · GitHub.
You’ll only need to flash the image, pair your device, grab a coffee and wait for initialization to finish.
What’s the advantage in comparison to using PiCroft?
Also, installing MyCroft without Docker wasn’t that complicated, I think.
Finer grained installation process (with autosetup of selected hardware components; say you have a google voice kit aiy ), auto login, auto git pull, …
Comes in handy if you struggle with the initial setup - and have no need to integrate mycroft in an existing environment / use it as a single purpose device.
Ah, OK, I understand. Very useful, thank you!