We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI seems flaky. Can be fixed later, though time="2021-09-21T14:19:05Z" level=fatal msg="failed to create shim: failed to mount rootfs component &{nullfs /var/lib/containerd/io.containerd.snapshotter.v1.native/snapshots/3 [rw]}: mount [[-o rw -t nullfs /var/lib/containerd/io.containerd.snapshotter.v1.native/snapshots/3 /run/containerd/io.containerd.runtime.v2.task/default/70886b2a11483b463360ab4f419294075698a64754c02bc1dda57fc642e60ba9/rootfs]] failed: "mount_nullfs: /run/containerd/io.containerd.runtime.v2.task/default/70886b2a11483b463360ab4f419294075698a64754c02bc1dda57fc642e60ba9/rootfs: Resource deadlock avoided\n": exit status 1: unknown"
CI seems flaky.
Can be fixed later, though
time="2021-09-21T14:19:05Z" level=fatal msg="failed to create shim: failed to mount rootfs component &{nullfs /var/lib/containerd/io.containerd.snapshotter.v1.native/snapshots/3 [rw]}: mount [[-o rw -t nullfs /var/lib/containerd/io.containerd.snapshotter.v1.native/snapshots/3 /run/containerd/io.containerd.runtime.v2.task/default/70886b2a11483b463360ab4f419294075698a64754c02bc1dda57fc642e60ba9/rootfs]] failed: "mount_nullfs: /run/containerd/io.containerd.runtime.v2.task/default/70886b2a11483b463360ab4f419294075698a64754c02bc1dda57fc642e60ba9/rootfs: Resource deadlock avoided\n": exit status 1: unknown"
Originally posted by @AkihiroSuda in #361 (comment)
The text was updated successfully, but these errors were encountered:
Tracking this issue in runj: samuelkarp/runj#30
Sorry, something went wrong.
Is this still an issue?
Seems not
No branches or pull requests
Originally posted by @AkihiroSuda in #361 (comment)
The text was updated successfully, but these errors were encountered: