Marvin Drees

It would still require write permissions to actually allow commenting. That's why most jobs don't run right now.

> Looking good 👍 Is there anything else left to do or we can merge it? Please don't merge it yet. Code-wise there is nothing needed to do but as...

In my opinion we should have DCO and unit tests passing required as a bare minimum. Pushing and merging broken code (e.g. something that doesn't pass tests) should not be...

As this issue was opened 2021 there have been updates to oss-fuzz to allow native Go fuzzing as well: https://google.github.io/oss-fuzz/getting-started/new-project-guide/go-lang/#native-go-fuzzing-support So I would rather work on implementing that in favor...

Looks like it has been changed already according to https://github.com/dagger/dagger/pull/3962/files#diff-06f64a45e1c277b0b72114e68d6c0936525c046b63a5d969b53e4a60a6e553adL9 So should this issue be closed as well then?

The same issue occurs on Arch Linux as a host instead of Fedora so it is not caused by Fedora exclusively.

Still the same error message. Followed your steps as such: - First terminal `podman run --rm -ti --userns=keep-id --user 0 --name test arm64v8/ubuntu:18.04` - Inside container ran `apt update &&...

Looks like this is somewhat intended and there are known workarounds listed in this discussion here. I agree that we can close the issue here. https://github.com/containers/podman/discussions/20445

My current workflow consist of calling Task from inside Daggers Go-SDK. Maybe Task could leverage that to transparently execute tasks in Docker instead? It already gives you a way to...

> As long as we _finally_ get more flexible key support, including PKCS#11 (#427) and other options (#525), maybe even Yubikeys then you've got my +1 @rdimitrov 😉 > >...