Miroirs/Conty
1
0
Fork 0
mirror of https://github.com/Kron4ek/Conty synced 2024-12-26 09:58:38 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Kron4ek 2023-05-31 23:12:29 +05:00 committed by GitHub
parent 6b29f9c6b9
commit e8da3b7b72
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -258,10 +258,9 @@ Environment variables:
isolates X11 server with Xephyr. isolates X11 server with Xephyr.
The default is 1. The default is 1.
USE_OVERLAYFS Mounts a writable fuse-overlayfs filesystem on top USE_OVERLAYFS Mounts a writable unionfs-fuse filesystem on top
of the read-only squashfs/dwarfs image, allowing to of the read-only squashfs/dwarfs image, allowing to
modify files inside it. Fuse3 is required for this modify files inside it.
feature.
Overlays are stored in ~/.local/share/Conty. If you Overlays are stored in ~/.local/share/Conty. If you
want to undo any changes, delete the entire want to undo any changes, delete the entire
directory from there. directory from there.
@ -271,7 +270,7 @@ Environment variables:
if you are using an Nvidia GPU, the proprietary if you are using an Nvidia GPU, the proprietary
driver and encountering issues running graphical driver and encountering issues running graphical
applications. At least 2 GB of free disk space is applications. At least 2 GB of free disk space is
required. And fuse3 is required for this feature. required. This function is enabled by default.
USE_SYS_UTILS Tells the script to use squashfuse/dwarfs and bwrap USE_SYS_UTILS Tells the script to use squashfuse/dwarfs and bwrap
installed on the system instead of the builtin ones. installed on the system instead of the builtin ones.
@ -483,7 +482,7 @@ $ WINEFSYNC=1 ./conty.sh wine someapplication.exe
For example, if the version of your Nvidia kernel module is 460.56 and the libraries inside the container are from 460.67 version, then you won't be able to run graphical applications. For example, if the version of your Nvidia kernel module is 460.56 and the libraries inside the container are from 460.67 version, then you won't be able to run graphical applications.
There are three solutions to this problem: There are three solutions to this problem:
* The first and the easiest solution is to use the `NVIDIA_HANDLER` feature of Conty, it will automatically download and pass the appropriate driver version into the container. In the latest verison of Conty this feature is enabled by default and should fix the problem automatically. Fuse3 is required for this feature. It hasn't been extensively tested yet, so if it does not work for you, i would appreciate it if you could leave a feedback [here](https://github.com/Kron4ek/Conty/discussions/74), mentioning your Linux distro and Nvidia driver version. * The first and the easiest solution is to use the `NVIDIA_HANDLER` feature of Conty, it will automatically download and pass the appropriate driver version into the container. In the latest verison of Conty this feature is enabled by default and should fix the problem automatically. It hasn't been extensively tested yet, so if it does not work for you, i would appreciate it if you could leave a feedback [here](https://github.com/Kron4ek/Conty/discussions/74), mentioning your Linux distro and Nvidia driver version.
* The second solution is to install the same driver version as included inside Conty, which is usually the latest non-beta version. You can see the exact driver version in pkg_list.txt attached to each Conty release. Of course if your GPU is not supported by new drivers, this is not an option for you. * The second solution is to install the same driver version as included inside Conty, which is usually the latest non-beta version. You can see the exact driver version in pkg_list.txt attached to each Conty release. Of course if your GPU is not supported by new drivers, this is not an option for you.
* The third solution is to (re)build Conty and include the same driver version as installed on your system. Read the [How to create your own Conty executables](#how-to-create-your-own-conty-executables) section, you will need to edit the `create-arch-bootstrap.sh` script or use the `enter-chroot.sh` script to include a different driver version. For instance, if you want to include legacy 470xx or 390xx drivers, edit the `create-arch-bootstrap.sh` script and replace `nvidia-utils` and `lib32-nvidia-utils` with `nvidia-470xx-utils` and `lib32-nvidia-470xx-utils` (replace 470xx with 390xx if you need 390xx drivers) in the `video_pkgs` variable, and then build Conty following the instructions. * The third solution is to (re)build Conty and include the same driver version as installed on your system. Read the [How to create your own Conty executables](#how-to-create-your-own-conty-executables) section, you will need to edit the `create-arch-bootstrap.sh` script or use the `enter-chroot.sh` script to include a different driver version. For instance, if you want to include legacy 470xx or 390xx drivers, edit the `create-arch-bootstrap.sh` script and replace `nvidia-utils` and `lib32-nvidia-utils` with `nvidia-470xx-utils` and `lib32-nvidia-470xx-utils` (replace 470xx with 390xx if you need 390xx drivers) in the `video_pkgs` variable, and then build Conty following the instructions.
* Some Windows applications running under Wine complain about lack of free disk space. This is because under Conty root partition is seen as full and read-only, so some applications think that there is no free space, even though you might have plenty of space in your HOME. The solution is simple, just run `winecfg`, move to "Drives" tab and add your `/home` as an additional drive (for example, `D:`), and then install applications to that drive. More info [here](https://github.com/Kron4ek/Conty/issues/67#issuecomment-1460257910). * Some Windows applications running under Wine complain about lack of free disk space. This is because under Conty root partition is seen as full and read-only, so some applications think that there is no free space, even though you might have plenty of space in your HOME. The solution is simple, just run `winecfg`, move to "Drives" tab and add your `/home` as an additional drive (for example, `D:`), and then install applications to that drive. More info [here](https://github.com/Kron4ek/Conty/issues/67#issuecomment-1460257910).
@ -496,7 +495,7 @@ $ WINEFSYNC=1 ./conty.sh wine someapplication.exe
* [bubblewrap](https://github.com/containers/bubblewrap) * [bubblewrap](https://github.com/containers/bubblewrap)
* [squashfuse](https://github.com/vasi/squashfuse) * [squashfuse](https://github.com/vasi/squashfuse)
* [dwarfs](https://github.com/mhx/dwarfs) * [dwarfs](https://github.com/mhx/dwarfs)
* [fuse-overlayfs](https://github.com/containers/fuse-overlayfs) * [unionfs-fuse](https://github.com/rpodgorny/unionfs-fuse)
* [zstd](https://github.com/facebook/zstd) * [zstd](https://github.com/facebook/zstd)
* [busybox](https://busybox.net/) * [busybox](https://busybox.net/)
* [bash](https://www.gnu.org/software/bash/) * [bash](https://www.gnu.org/software/bash/)