Chris Evich

Hrmm, seems like you did things correctly, checking why it failed. Also FYI: If you force-push/cancel any running VM build tasks are still running, they sometimes (annoyingly/unfortunately) leave behind running...

I re-ran the two failed container image build tasks. They failed due to a quay.io flake: "Error: writing blob: initiating layer upload to /v2/libpod/ccia/blobs/uploads/ in quay.io: received unexpected HTTP status:...

I met with him the other day, he's going to need some guidance. My understanding is the intent is to use the new fedora-podman-py image in the podman-py repo. Though...

Hitting this also, it's a deal-breaker. Cannot use hadolint b/c this.

Thank you so much @afro-coder for taking the initiative to open this issue and get this effort started! Some logistics tips in case they help: - The podman.io site comes...

> Ah this is confusing Precisely why I wrote it :grin: > Can we use this as an issue tracker for the smaller issues in different repos? I'm not sure...

> start a spreadsheet listing documentation tasks If it helps, I believe it's possible to make those documents open for public editing? If that's a bad idea, there's also the...

@dashea I re-ran two tests that had flakes - "quay: 503 gateway timeout". Quay is notoriously flaky on these older branches. In podman CI too.

Would this address #5988 also or is that something different?

[Initial test-run](https://cirrus-ci.com/build/4881385851191296) * [All but one (not a flake) of the Mac PM tests](https://api.cirrus-ci.com/v1/artifact/task/5839717474762752/html/mac-libkrun-podman-darwin-rootless-host-sqlite.log.html#t--run-basic-podman-commands-Volume-ops--1) pass w/ libkrun. Looked at the code for the failure, can't understand the test or why...