![]() ![]() I assume it does not work because the way SQLite does locking/wal writes is by using the same OS, and docker for Mac M1 is probably emulating complete second OS with a Linux kernel. ![]() (At the cost of performance. MacOS > 12.4 QEMU > 7.0. It has been mentioned that when employing x8664 Docker images on an M1 Mac, when no ARM64 image is available, that container will start under qemu emulation for compatibility. Test with Apple Silicon / M1 and CentOS aarch64 image - GitHub - ppggff/vagrant-qemu: Use Vagrant to manage machines using QEMU. I am getting strange results the process continues as if it can write to the database, but both inside of and outside of the container sqlite3 seems to show a frozen version of the file (not showing the most recent writes). Use Vagrant to manage machines using QEMU. When Docker for M1 runs based amd64 containers, I think it uses QEMU to emulate a amd64 CPU on the arm based M1.īut the issue I have is that there is SQLite code running inside the container, writing to a DB file that should be persisted to the host disk (I assume via some sort of feature to share directories host->QEMU). (Image credit: Apple) Since you can already run Linux on ARM, it was only a matter of time before someone found a way to get the open source operating system working on the new Arm-based M1 Macs. I am running a container, sharing a directory from my host to the guest:ĭocker run -platform -v /m1-host-dir:/vol linux/amd64 ubuntu ![]() My computer is a Mac M1, I have Docker Desktop installed. ![]()
0 Comments
Leave a Reply. |