That’s nice to hear, @joao.cabrita! When do we plan on using Docker deployments for all new Ocim instances? Or is this not the same thing? If this affects deployment time, we’ll probably need to update our standard estimates, cc. @Fox
@gabriel These changes don’t create docker images for Open edX deployments. They just make OCIM itself able to run in a container for development, rather than Vagrant, which is slower and less supported across processor architectures. This is important because more of our developers are beginning to, or are looking at, switching to computers running the ARM architecture rather than the x86_64 architecture. Most notably, Apple’s new Macbooks.
Yep, IMO we’re most likely to see the impact of this on time spent working on OCIM changes because setting up a new dev environment is faster (and easier for newcomers and non-OpenCraft contributors).
It might also set the stage for deploying OCIM itself in a container but, since I’m not familiar with how it’s deployed at the moment, I can only speculate on what the economics of that look like.