podman/vendor/github.com/Microsoft/go-winio
Nick Guenther 572e6464f6 Use storage that better supports rootless overlayfs
overlayfs -- the kernel's version, not fuse-overlayfs -- recently learned
(as of linux 5.16.0, I believe) how to support rootless users. Previously,
rootless users had to use these storage.conf(5) settings:

* storage.driver=vfs          (aka STORAGE_DRIVER=vfs), or
* storage.driver=overlay      (aka STORAGE_DRIVER=overlay),
  storage.options.overlay.mount_program=/usr/bin/fuse-overlayfs
                              (aka STORAGE_OPTS=/usr/bin/fuse-overlayfs)

Now that a third backend is available, setting only:

* storage.driver=overlay      (aka STORAGE_DRIVER=overlay)

https://github.com/containers/podman/issues/13123 reported EXDEV errors
during the normal operation of their container. Tracing it out, the
problem turned out to be that their container was being mounted without
'userxattr'; I don't fully understand why, but mount(8) mentions this is
needed for rootless users:

> userxattr
>
>   Use the "user.overlay." xattr namespace instead of "trusted.overlay.".
>   This is useful for unprivileged mounting of overlayfs.

https://github.com/containers/storage/pull/1156 found and fixed the issue
in podman, and this just pulls in that via

    go get github.com/containers/storage@ebc90ab
    go mod vendor
    make vendor

Closes https://github.com/containers/podman/issues/13123

Signed-off-by: Nick Guenther <nick.guenther@polymtl.ca>
2022-03-01 12:09:42 -05:00
..
backuptar Use storage that better supports rootless overlayfs 2022-03-01 12:09:42 -05:00
pkg Use storage that better supports rootless overlayfs 2022-03-01 12:09:42 -05:00
vhd Use storage that better supports rootless overlayfs 2022-03-01 12:09:42 -05:00
.gitignore migrate to go-modules 2019-06-24 13:20:59 +02:00
CODEOWNERS Bump github.com/containers/storage from 1.25.0 to 1.28.0 2021-03-18 20:27:25 +01:00
LICENSE Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
README.md image lookup: do not match *any* tags 2021-11-23 11:15:03 +01:00
backup.go Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
ea.go vendor: update everything 2019-01-11 13:38:11 +01:00
file.go Use storage that better supports rootless overlayfs 2022-03-01 12:09:42 -05:00
fileinfo.go Bump github.com/containers/storage from 1.25.0 to 1.28.0 2021-03-18 20:27:25 +01:00
go.mod Use storage that better supports rootless overlayfs 2022-03-01 12:09:42 -05:00
go.sum Use storage that better supports rootless overlayfs 2022-03-01 12:09:42 -05:00
hvsock.go Use storage that better supports rootless overlayfs 2022-03-01 12:09:42 -05:00
pipe.go Bump github.com/containers/storage from 1.24.3 to 1.24.4 2020-12-23 04:29:57 -05:00
privilege.go Bump github.com/containers/storage from 1.31.1 to 1.31.2 2021-05-21 07:25:04 +00:00
reparse.go Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
sd.go Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
syscall.go Bump github.com/containers/storage from 1.25.0 to 1.28.0 2021-03-18 20:27:25 +01:00
zsyscall_windows.go Bump github.com/containers/storage from 1.25.0 to 1.28.0 2021-03-18 20:27:25 +01:00

README.md

go-winio Build Status

This repository contains utilities for efficiently performing Win32 IO operations in Go. Currently, this is focused on accessing named pipes and other file handles, and for using named pipes as a net transport.

This code relies on IO completion ports to avoid blocking IO on system threads, allowing Go to reuse the thread to schedule another goroutine. This limits support to Windows Vista and newer operating systems. This is similar to the implementation of network sockets in Go's net package.

Please see the LICENSE file for licensing information.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

We also require that contributors sign their commits using git commit -s or git commit --signoff to certify they either authored the work themselves or otherwise have permission to use it in this project. Please see https://developercertificate.org/ for more info, as well as to make sure that you can attest to the rules listed. Our CI uses the DCO Github app to ensure that all commits in a given PR are signed-off.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Special Thanks

Thanks to natefinch for the inspiration for this library. See https://github.com/natefinch/npipe for another named pipe implementation.