Aleksa Sarai

Also it seems that the 32-bit zip file in the 1.0.1 release is actually 64-bit, so I had to use the 1.0.0 release. ``` % unzip ../textractor_x86.zip Archive: ../textractor_x86.zip inflating:...

I've started seeing this in my NextCloud logs, in case that helps. :sweat_smile: ``` [core] Error: Error while running background job OC\Preview\BackgroundCleanupJob (id: 21, arguments: null) from ? by --...

@Zheaoli You'll need to base it on top of #3985, which reworks all of the mountfd logic. I'm not sure how easy it'll be to use the new Go-based setup...

> I thought we worked around that by using runtime.GOMAXPROCS(1) in runc init code but this is not enough. This doesn't guarantee we won't get new threads, it just tries...

Does it need to be backported? We will do a 1.2 release soon:tm: (probably in March, when I get back from vacation) so the problem will be in a fixed...

What is your `config.json`? In particular, do you have `terminal` enabled or disabled?

(We really need to document this somewhere other than issues, or I should come up with a canned reply to questions about `terminal`.) There are three main cases that can...

@deitch > I couldn’t figure that out either. What gets passed? The path to a Unix domain socket, ok, but is that socket itself intended to become one of stdout...

@thaJeztah Yeah we probably should have a `docs` (https://runc.io/ used to be our "soft" documentation, but it looks like that website has been taken down and now just points to...

@deitch > Is that it? Why didn’t it just let me pass to it —stdin dev —stdout dev —stderr dev instead of the whole complex “have runc create it and...