Package Details: nvidia-container-toolkit 1.3.0-1

Git Clone URL: (read-only, click to copy)
Package Base: nvidia-container-toolkit
Description: NVIDIA container runtime toolkit
Upstream URL:
Keywords: docker nvidia nvidia-docker runc
Licenses: Apache
Conflicts: nvidia-container-runtime<2.0.0, nvidia-container-runtime-hook
Replaces: nvidia-container-runtime-hook
Submitter: jshap
Maintainer: jshap (kiendang)
Last Packager: jshap
Votes: 15
Popularity: 3.05
First Submitted: 2019-07-28 01:19
Last Updated: 2020-09-23 17:13

Pinned Comments

jshap commented on 2019-07-28 01:43

see the release notes here for why this exists:

tl;dr: nvidia-docker is deprecated because docker now has native gpu support, which this package is required to use. :)

Latest Comments

1 2 3 Next › Last »

kiendang commented on 2020-07-14 11:44

@yosunpeng you can edit the PKGBUILD and add GOPROXY= to the go build command

GOPATH="${srcdir}/gopath" \
  go build -v \

yosunpeng commented on 2020-07-14 07:53

I got an error while installing this package.

go: Get "": dial tcp: lookup Temporary failure in name resolution
==> ERROR: A failure occurred in build().

It seems that China's GFW bans Is there any possible to skip this step or use mirror web server? Please help, thank you!

kipsora commented on 2020-07-02 18:10

I also modified the checksums by hand and also got sucked by the _srcdir issue. Finally got my hands dirty by changing _srcdir to nvidia-container-toolkit-${pkgver} (and need to manually decompress the tarball). But that's only a workaround. Hope the maintainer of this package fix these issues soon.

hanielxx commented on 2020-07-02 07:40

I've fixed it via changing the sha256sums manually and rebuilding.

Another problem is that _srcdir should be "nvidia-container-toolkit-${pkgver}".

hanielxx commented on 2020-07-02 05:28

The following error occured when i tried to install it:

$ yay -S nvidia-container-toolkit
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur: 1]  nvidia-container-toolkit-1.1.2-1

  1 nvidia-container-toolkit                 (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> n
:: PKGBUILD up to date, Skipping (1/1): nvidia-container-toolkit
  1 nvidia-container-toolkit                 (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> n
:: Parsing SRCINFO (1/1): nvidia-container-toolkit
==> Making package: nvidia-container-toolkit 1.1.2-1 (2020年07月**日 *****)
==> Retrieving sources...
  -> Downloading v1.1.2.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   138  100   138    0     0     31      0  0:00:04  0:00:04 --:--:--    31
100   139  100   139    0     0     28      0  0:00:04  0:00:04 --:--:--  135k
100 1703k    0 1703k    0     0  19245      0 --:--:--  0:01:30 --:--:-- 15403
==> Validating source files with sha256sums...
    v1.1.2.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: nvidia-container-toolkit

What's more, the sha256sums generated by makepkg -g is not consistent with that in PKGBUILD.

What can i do to install it?

I tried (SOLVED) error "One or more files did not pass the validity check!", but it also failed.

glvr182 commented on 2020-03-11 16:08

When GO111MODULE is set to on, the build failed with the following error: can't load package: package nvidia-container-toolkit is not in GOROOT (/usr/lib/go/src/nvidia-container-toolkit)

A way to fix this is to set GO111MODULE to off during the build step:

GOPATH="${srcdir}/gopath" GO111MODULE=off go build -v \
                            -buildmode=pie \
                            -gcflags "all=-trimpath=${PWD}" \
                            -asmflags "all=-trimpath=${PWD}" \
                            -ldflags "-extldflags ${LDFLAGS}" \

hantian_pang commented on 2019-12-13 04:29

error log like this:

/usr/bin/ld: /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/usr/lib/libelf.a(elf_scn.o): in function `_libelf_load_section_headers':

/home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/src/elftoolchain-0.7.1/libelf/elf_scn.c:72: undefined reference to `_libelf_fsize'

/usr/bin/ld: /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/usr/lib/libelf.a(gelf_fsize.o): in function elf32_fsize': /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/src/elftoolchain-0.7.1/libelf/gelf_fsize.c:37: undefined reference to_libelf_fsize'

/usr/bin/ld: /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/usr/lib/libelf.a(gelf_fsize.o): in function elf64_fsize': /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/src/elftoolchain-0.7.1/libelf/gelf_fsize.c:43: undefined reference to_libelf_fsize'

/usr/bin/ld: /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/usr/lib/libelf.a(gelf_fsize.o): in function gelf_fsize': /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/src/elftoolchain-0.7.1/libelf/gelf_fsize.c:56: undefined reference to_libelf_fsize'

/usr/bin/ld: /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/usr/lib/libelf.a(libelf_ehdr.o): in function `_libelf_load_extended':

/home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/src/elftoolchain-0.7.1/libelf/libelf_ehdr.c:52: undefined reference to `_libelf_fsize'

/usr/bin/ld: /home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/usr/lib/libelf.a(libelf_ehdr.o):/home/pang/.cache/pikaur/build/libnvidia-container/src/libnvidia-container-1.0.5/deps/src/elftoolchain-0.7.1/libelf/libelf_ehdr.c:138: more undefined references to `_libelf_fsize' follow

jshap commented on 2019-11-06 06:43

@ruro no worries, I actually forgot that gcc-go exists. I was just trying to make things cleaner, the other flags should already be handling it anyways so it's really a non-issue :)

ruro commented on 2019-11-06 06:03

@jshap ah, yes, my bad. I thought, that I checked that I had the latest go, but apparently I must have misread the version.

Although, I am indeed not using Arch, but Manjaro, I think the issue is not that.

I have core/gcc-go 9.2.0-3 installed instead of community/go 2:1.13.4-1. Apparently, core/gcc-go provides go=1.12.2.

jshap commented on 2019-11-06 02:17

@ruro guessing not arch? since go 1.13 that flag is available :(

I'll remove it though.