summaryrefslogtreecommitdiff
path: root/Dockerfile.Fedora
diff options
context:
space:
mode:
authorW. Trevor King <wking@tremily.us>2018-05-10 21:38:53 -0700
committerAtomic Bot <atomic-devel@projectatomic.io>2018-05-11 15:07:14 +0000
commit608f0b9596cf8f0913c4a086eeed654b589f79f4 (patch)
treea311af398af849293b28bb40c3cea76c58a35616 /Dockerfile.Fedora
parent177c27e75dccdc64f488c240948ad6de88383a29 (diff)
downloadpodman-608f0b9596cf8f0913c4a086eeed654b589f79f4.tar.gz
podman-608f0b9596cf8f0913c4a086eeed654b589f79f4.tar.bz2
podman-608f0b9596cf8f0913c4a086eeed654b589f79f4.zip
vendor.conf: Pin containernetworking/plugins to 1fb94a42
containernetworking/plugins@a0eac8d7 (pkg/ns: remove namespace creation, 2018-03-16) removed NewNS, which we use in libpod/networking.go. Pinning to the previous commit, containernetworking/plugins@1fb94a42 (Merge pull request #96 from DennisDenuto/denuto/master, 2018-03-14), allows us to run vndr without breaking our build. This is a short term fix; moving forward we'll want to either drop this dependency or catch up with the new upstream API. The upstream package seems to have been fairly stable in the meantime, because even with the new pinned version, a vndr re-vendor generates no changes: $ vndr github.com/containernetworking/plugins Signed-off-by: W. Trevor King <wking@tremily.us> Closes: #751 Approved by: mheon
Diffstat (limited to 'Dockerfile.Fedora')
0 files changed, 0 insertions, 0 deletions