Package Details: gvisor-bin 20241007.0-1

Git Clone URL: https://aur.archlinux.org/gvisor-bin.git (read-only, click to copy)
Package Base: gvisor-bin
Description: OCI container sandbox runtime focused on security, efficiency, and ease of use
Upstream URL: https://gvisor.dev
Keywords: containers docker oci runsc runtime sandbox security user-space
Licenses: Apache-2.0
Conflicts: gvisor
Provides: gvisor
Submitter: None
Maintainer: SunRed
Last Packager: SunRed
Votes: 4
Popularity: 0.000001
First Submitted: 2020-02-02 19:47 (UTC)
Last Updated: 2024-10-09 21:14 (UTC)

Latest Comments

1 2 Next › Last »

SunRed commented on 2022-05-22 19:54 (UTC)

There seems to be an issue again with their CI not building the latest release tags.

SunRed commented on 2022-04-30 17:47 (UTC)

Since this issue was finally resolved, the new version now supports the systemd cgroup driver. This was actually supported since the end of March but their version was stuck at 20220228 before this issue was addressed.

linuxyeet commented on 2021-12-10 12:20 (UTC) (edited on 2021-12-10 12:22 (UTC) by linuxyeet)

After receiving the same error as many people:

docker: Error response from daemon: failed to create shim: OCI runtime create failed: unable to retrieve OCI runtime error (open /var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/fc9b49276ad1768844fce24c42a8e04a1673b2733b0858ca31fcb6bbe228dd26/log.json: no such file or directory): /usr/bin/runsc did not terminate successfully: exit status 1: unknown.

i found a fix after comparing the docker configuration to my ubuntu install where gvisor worked fine.

Add the following property/line to /etc/docker/daemon.json:

"exec-opts": ["native.cgroupdriver=cgroupfs"]

By default arch uses systemd as a driver, which apparently is incompatible to gvisor

After a sudo systemctl restart docker i can run the hello world program perfectly fine (sudo docker run --rm --runtime=runsc hello-world)

unknowndev commented on 2021-11-03 12:58 (UTC)

Also, I noticed that pre_upgrade() can be removed because runsc install resets things about runsc

unknowndev commented on 2021-11-03 12:28 (UTC)

@braderhart Executing runsc uninstall or runsc install after adding runsc's runtimeArgs will cause the runtimeArgs to be deleted

<deleted-account> commented on 2021-11-01 18:38 (UTC) 

Imbalance of power corrupts and monopoly of power corrupts absolutely.
        -- Genji

unknowndev commented on 2021-10-30 08:14 (UTC)

@braderhart The current solution meets my needs, it would be nice to put runc install in another package, because my daemon.json doesn't want to be changed by runsc

<deleted-account> commented on 2021-06-30 17:07 (UTC)

Behold the warranty -- the bold print giveth and the fine print taketh away.

unknowndev commented on 2021-06-30 11:55 (UTC) (edited on 2021-06-30 11:55 (UTC) by unknowndev)

With the recent podman update, users can use runsc directly without making any changes, and docker is not the only example available on the gVisor website

example: https://gvisor.dev/docs/user_guide/quick_start/oci/

@braderhart

1 2 Next › Last »