You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All of the macOS tests that involve installing Docker are flaky because the installation step is fragile
Due to a known Docker issue we have to lock the version to 4.10.0 to be able to use it in CI
We have spent several man-hours debugging and patching the two points above
How:
Colima is a container runtime for macOS, it's an alternative to installing the Docker.app in macOS, with great CLI support.
Colima is included by default in GitHub macOS runners, we did a PoC a while ago and there were some incompatibilities that caused CI to fail, the goal of this issue is to give it another try, and make the necessary adjustments to make it work.
As the scope of work is very uncertain, please timebox this (~half a day) to see if we can have more clarity on what would be necessary.
Questions:
Maybe we still want to use Docker.app for fleetctl preview? this way we simulate the way that people will actually use it
The text was updated successfully, but these errors were encountered:
lucasmrod
changed the title
investiagate using Colima as the container runtime for macOS runners in CI
Investigate using Colima as the container runtime for macOS runners in CI
Oct 12, 2022
Motivation:
How:
Colima is a container runtime for macOS, it's an alternative to installing the Docker.app in macOS, with great CLI support.
Colima is included by default in GitHub macOS runners, we did a PoC a while ago and there were some incompatibilities that caused CI to fail, the goal of this issue is to give it another try, and make the necessary adjustments to make it work.
As the scope of work is very uncertain, please timebox this (~half a day) to see if we can have more clarity on what would be necessary.
Questions:
fleetctl preview
? this way we simulate the way that people will actually use itThe text was updated successfully, but these errors were encountered: