Try this new flow out for yourself, I found I spent a lot less time copying over everything manually via SSH or USB. It might have something to do with Docker for Mac's limitations but currently I have no workaround for this. Why!? I should see No such file or directory instead. images/retropie-4.1-rpi2_rpi3.img in MacOS and then in the Docker container I do ls -al /workspace/images/retropie-4.1-rpi2_rpi3.img and I see this: -rw-r-r- 0 root root 10737418240 Mar 5 21:36 /workspace/images/retropie-4.1-rpi2_rpi3.img
#HOW TO INSTALL RETROPIE IMAGE MAC#
images volume were seemingly gone from both Mac and the Docker container. Whilst testing with Docker for Mac, deleted files from the. See the docker installation guide for help installing it. Now the whole process is fast and simple! The solution is using Docker too so it works with MacOS, Windows and Linux.
![how to install retropie image how to install retropie image](https://i.ytimg.com/vi/J1fGwdXcKT4/maxresdefault.jpg)
Afterwards I would take my sdcard back and make a backup of it which created a new image I could then reuse. I would burn the base RetroPie image to my sdcard, then I would copy any roms or BIOS over. Building your own custom RetroPie image can be really slow, so I created a simpler way to do it using Docker and bash scripts - introducing docker-build-retropie-image! WhyĬreating custom prebuilt images was becoming painful.