mirabilos comments

Results 383 comments of


                                            mirabilos

docker: Error response from daemon: OCI runtime create failed: /var/lib/docker/runtimes/runsc did not terminate sucessfully: creating container: fork/exec /proc/self/exe: operation not permitted

Fabricio Voznika dixit: >Check that `/usr/local/bin/runsc` has execute access given to all. The -r-xr-xr-x 1 root bin 19246606 Mär 19 22:17 /usr/local/bin/runsc* Sure.

docker: Error response from daemon: OCI runtime create failed: /var/lib/docker/runtimes/runsc did not terminate sucessfully: creating container: fork/exec /proc/self/exe: operation not permitted

Fabricio Voznika dixit: >Hmm..., the log shows that the gofer process (which runs as the same >user) was able to be started correctly. But the sandbox, which runs >with a...

docker: Error response from daemon: OCI runtime create failed: /var/lib/docker/runtimes/runsc did not terminate sucessfully: creating container: fork/exec /proc/self/exe: operation not permitted

Fabricio Voznika dixit: >Is there anything in your configuration I don’t have a configuration, asides from what is mentioned on the gvisor site (as I freshly installed Docker specifically to...

docker: Error response from daemon: OCI runtime create failed: /var/lib/docker/runtimes/runsc did not terminate sucessfully: creating container: fork/exec /proc/self/exe: operation not permitted

I believe you’re on to something: ``` (sid-amd64)tglase@tglase:~ $ sudo unshare -Ur true && echo PASS; [sudo] password for tglase: unshare: unshare failed: Operation not permitted (sid-amd64)1|tglase@tglase:~ $ sudo unshare...

docker: Error response from daemon: OCI runtime create failed: /var/lib/docker/runtimes/runsc did not terminate sucessfully: creating container: fork/exec /proc/self/exe: operation not permitted

``` (sid-amd64)tglase@tglase:~ $ sudo unshare -U true && echo PASS; unshare: unshare failed: Operation not permitted (sid-amd64)1|tglase@tglase:~ $ sudo unshare -n true && echo PASS; PASS ``` What should I...

docker: Error response from daemon: OCI runtime create failed: /var/lib/docker/runtimes/runsc did not terminate sucessfully: creating container: fork/exec /proc/self/exe: operation not permitted

Hm, that’s bad… I cannot test outside of the chroot as docker is not available for x32… I guess I’ll have to fire up a VM for that then. Since...

docker: Error response from daemon: OCI runtime create failed: /var/lib/docker/runtimes/runsc did not terminate sucessfully: creating container: fork/exec /proc/self/exe: operation not permitted

It’s not so easy… my actual setup is an `schroot` instance, not a simple call to chroot, with a persistent session running, dæmons in the background, and optionally multiple shells...

docker: Error response from daemon: OCI runtime create failed: /var/lib/docker/runtimes/runsc did not terminate sucessfully: creating container: fork/exec /proc/self/exe: operation not permitted

No, that commit has nothing to do with this issue.

[bug/performance] Slow Postgres `COUNT(*)` queries

> Unfortunately it's part of the Mastodon API Yeah, grml… ok. But please put in an estimate instead. The linked document explains both why `COUNT(*)` is necessarily slow in PostgreSQL...

[bug/performance] Slow Postgres `COUNT(*)` queries

Oh hmm. Estimating with a filter (on account) is ofc not as easily possible. I’d settle for a hack: a config option that makes it just return 0 posts for...