Alex Pyrgiotis

I've fixed most of my issues (I think I have only one left). The main problem however is that the `master` branch of `django-eztables` itself cannot pass the tests, probably...

The PR has been updated with a commit that fixes the failing tests that have to do with the url resolving. Briefly put, the problem occurred in tests that requested...

Yes, I believe that the fix you proposed is much cleaner and consistent with the Django documentation.

Hi @noirbizarre, I had some time today to work on this pull request. I have added some documentation for the features that this pull request introduces (client-side processing, custom formatting,...

I used the `-debug-log` switch, and I'm now seeing more logs. The following logs from the gofer process provide more info: ``` I1116 12:05:48.419039 1 main.go:216] *************************** I1116 12:05:48.419097 1...

I see that the relevant check in Gofer happens here: https://github.com/google/gvisor/blob/d8aa09e04c4e38155dfcee6ed0495c2b29f604fc/runsc/cmd/gofer.go#L418 Since we are already running in rootless Podman, we may opt to reuse the existing `/proc` and `/` paths....

Unfortunately not. I haven't managed to work more in this front actually.

Doesn't look like it I'm afraid. The original invocation (`runsc -debug -network none -rootless do echo ok`) still **fails** with: ``` I1110 09:32:21.865885 1 main.go:189] *************************** I1110 09:32:21.865967 1 main.go:190]...

Oh, that's great! Thanks a lot for the progress on this front. @terenceli, just to be sure, did this fix work within a rootless Podman container, as described at the...

Thanks a lot @terenceli. Unfortunately I didn't have time to test it on my own, but the results look promising! For our use case (Dangerzone) we are spinning up containers...