Phil Estes
Phil Estes
@StefanScherer I'm curious now that we are in 2021 if I can get something assembled with GH Actions (Windows runners) to have an easier way to do this in context...
I now have these 2 covered: ``` - windows/amd64:10.0.17763.1817 - windows/amd64:10.0.14393.4283 ``` in the v0.4.0 release which is built from this [github release action](https://github.com/estesp/mquery/blob/v0.4.0/.github/workflows/release.yml). The Dockerfiles for Windows are [here...
I should also mention I have not tested those images on any Windows system, although they were built with Docker on a Windows 2019 node in GitHub Actions. :)
So, we can do the same thing here we do in containerd (have a `/release/1.0.x` branch anchored at the recent v1.0.3 tag that cuts all future 1.0.x releases) but I...
Definitely possible if we need to; cgroups v2 tests are much less intensive than the containerd overall project. My PR that just updated Go and the Fedora version ran vagrant...
#7464 is the backport for `release/1.5` and will be merged and available in a future 1.5.x release
Seems this patch must introduce a logic error with config env vars; all CI runs are now failing the test `TestContainerSpecDefaultPath`
Since this is effectively a bug fix, we should put it into our supported release branches
@MikeZappa87 if this is still valid, we should get this in..looks like it fell between the cracks
With v2.1.0 release, there is now JSON output with `--raw` and even OCI config expansion when adding `--expand-config`. Let me know if there are any additional concerns here.