Vincent van Dam

@aramase thanks for the suggestion. This is a similar approach as using the az cli to get the the values and creating the azure identity resource. It is not that...

Not sure either, maybe it's the verbosity flag, does it occur with `-v 1` as well?

It seems to replace and create files that need root permissions, I think this is the reason why it fails in OpenShift (where containers typically are enforced to not run...

By default, OpenShift does not run containers with the root uid/gid, but takes an arbitrary uid instead. This also applies on tekton tasks; they are run as an arbitrary user....

Ah, this is an oversight in the cleaning. Configmaps are only used when `--pre-archive` or `--lock` are used, the reaper is unaware of this and tries to clean these as...

Thanks, I updated the documentation accordingly.

I have improved the container status api endpoint, can you validate if this solves the issue?

Locally using minikube the test doesn't fail for me. Are you using OpenShift? Upping the verbosity (e.g. `kubedock server -P -v 5 --port-forward`) displays what the startup actually does; it...

When running kubedock to enforce user 1001, the test fails indeed. This is because it tries to copy a shell script to /, which is not allowed by that user....

It doesn't look to be the case always and I haven't been able to reproduce myself. Do you have a small project which can trigger this behaviour?