NVIDIA_HANDLER discussion

[Kron4ek]

Please share your experience with the NVIDIA_HANDLER function.

[VHSgunzo]

@Kron4ek
The new function looks too overcomplicated. Although most likely there is no easy way to solve this problem, my version of the solution also shows this)
But I want to note that I did tests of the speed of reading files from the my container in packed mode and in packed mode + fuse-overlayfs, so in the second case, the speed drops a lot (2-2.5x)

[VHSgunzo]

@Kron4ek
Look at the total time:

[Kron4ek]

@VHSgunzo Fuse-overlayfs adds a big delay here. I searched for faster alternatives and found out that unionfs-fuse works significantly faster than fuse-overlayfs, so i will use it.

[VHSgunzo]

hmm interesting, I need to check it out too

[VHSgunzo]

@Kron4ek
I did a little tests.
Yes, unionfs-fuse is faster than fuse-overlayfs, but it's still 1.5x slower than using a complex bind/mount function

[Kron4ek]

1.5x is tolerable, i think.

[VHSgunzo]

@Kron4ek
There is another point that you may have missed, is the installation of packages in the mandatory dependencies of which are Nvidia packages from the archlinux repository. In this situation, most likely, conflicts of exists in filesystem will occur.
like this for ocl-icd

ocl-icd: /usr/bin/cllayerinfo exists in filesystem
ocl-icd: /usr/lib/libOpenCL.so exists in filesystem
ocl-icd: /usr/lib/libOpenCL.so.1 exists in filesystem
ocl-icd: /usr/lib/libOpenCL.so.1.0.0 exists in filesystem
ocl-icd: /usr/lib/pkgconfig/OpenCL.pc exists in filesystem
ocl-icd: /usr/lib/pkgconfig/ocl-icd.pc exists in filesystem
ocl-icd: /usr/share/doc/ocl-icd/examples/ocl_icd_bindings.c exists in filesystem
ocl-icd: /usr/share/doc/ocl-icd/html/libOpenCL.html exists in filesystem
ocl-icd: /usr/share/licenses/ocl-icd/COPYING exists in filesystem

or for cuda (depend on nvidia-utils)
and some package depend on NVIDIA-MODULE
Which are not provided using current methods of solving the problem with Nvidia in Conty.

Although, it seems that Conty is broken in the database part of installed pacman packages, since installing almost any package will cause errors exists in filesystem

...
glibc: /usr/lib/gconv/ASMO_449.so exists in filesystem
glibc: /usr/lib/gconv/BIG5.so exists in filesystem
glibc: /usr/lib/gconv/BIG5HKSCS.so exists in filesystem
glibc: /usr/lib/gconv/BRF.so exists in filesystem
glibc: /usr/lib/gconv/CP10007.so exists in filesystem
glibc: /usr/lib/gconv/CP1125.so exists in filesystem
glibc: /usr/lib/gconv/CP1250.so exists in filesystem
glibc: /usr/lib/gconv/CP1251.so exists in filesystem
glibc: /usr/lib/gconv/CP1252.so exists in filesystem
glibc: /usr/lib/gconv/CP1253.so exists in filesystem
glibc: /usr/lib/gconv/CP1254.so exists in filesystem
glibc: /usr/lib/gconv/CP1255.so exists in filesystem
glibc: /usr/lib/gconv/CP1256.so exists in filesystem
glibc: /usr/lib/gconv/CP1257.so exists in filesystem
glibc: /usr/lib/gconv/CP1258.so exists in filesystem
glibc: /usr/lib/gconv/CP737.so exists in filesystem
glibc: /usr/lib/gconv/CP770.so exists in filesystem
glibc: /usr/lib/gconv/CP771.so exists in filesystem
glibc: /usr/lib/gconv/CP772.so exists in filesystem
glibc: /usr/lib/gconv/CP773.so exists in filesystem
glibc: /usr/lib/gconv/CP774.so exists in filesystem
....

[Kron4ek]

The only correct way to install packages via pacman to an already built Conty image is to use the '-u' argument:

$ ./conty.sh -u packagename1 packagename2 packagename3 ...

Installation through unionfs is not supported currently.