![\"\"](\"https:\/\/storage.deepin.org\/thread\/202406060535438081_en.png\")
<\/p>\nAs a new type of independent package management toolkit, Linglong primarily provides a layered and isolated operating environment, addressing compatibility issues caused by strong dependencies in traditional package management systems, as well as security issues resulting from lax permissions. Currently, Linglong supports four distributions, including deepin, UnionTech UOS, Debian, and Ubuntu. Linglong's isolation technology can completely decouple applications from the system, thereby thoroughly resolving compatibility conflicts between the system and applications, and among applications themselves, caused by upgrades and adaptation. For developers, this can effectively reduce development costs; for customers, it can reduce enterprise operational costs; and for the entire industry, it will help the industry to develop steadily.<\/p>\n
<\/p>\n
Install Linglong<\/strong><\/h1>\nThis article will introduce the installation of Linglong on UOS 1070 and deepin V23.<\/p>\n
\nNote: This document is applicable to version 1.5.0, please use\u00a0 \"ll-cli -- version\" \u00a0to check your Linglong program version.<\/p>\n<\/blockquote>\n
Linglong consists of three parts:<\/p>\n
\n- ll-builder is used for building and debugging Linglong applications, provided by linglong-builder;<\/li>\n
- ll-box is a sandbox container, provided by linglong-box;<\/li>\n
- ll-cli is for managing and running Linglong applications, provided by linglong-bin.<\/li>\n<\/ul>\n
<\/p>\n
1\u3001UOS 1070<\/strong><\/h2>\nCurrently supports amd64, arm64, and loongarch64 (Loongson old world) architectures.<\/p>\n
1)\u00a0 Add Linglong repository source<\/strong><\/p>\necho\u00a0\"deb [trusted=yes] https:\/\/ci.deepin.com\/repo\/deepin\/deepin-community\/linglong-repo\/ unstable main\"\u00a0|\u00a0sudo\u00a0tee\u00a0-a\u00a0\/etc\/apt\/sources.list<\/p><\/blockquote>\n
2) Install the Linglong build toolkit<\/strong><\/p>\nsudo\u00a0apt\u00a0update<\/p>\n
sudo\u00a0apt\u00a0install\u00a0linglong-builder\u00a0linglong-box\u00a0linglong-bin<\/p><\/blockquote>\n
<\/p>\n
2\u3001deepin V23<\/strong><\/h2>\nCurrently supports amd64 and arm64 architectures.<\/p>\n
sudo\u00a0apt\u00a0install\u00a0linglong-builder\u00a0linglong-box\u00a0linglong-bin<\/p><\/blockquote>\n
<\/p>\n
Install the Pica Tool<\/strong><\/h1>\nThis tool currently offers the capability to convert deb packages into Linglong packages, generate the linglong.yaml file needed for building Linglong applications, and relies on ll-builder to implement application building and exportation.<\/p>\n
1\u3001UOS 1070<\/strong><\/h2>\nCurrently supports amd64 and arm64 architectures.<\/p>\n
According to the Linglong installation steps, add the Linglong repository source.<\/p>\n
sudo\u00a0apt\u00a0install\u00a0linglong-pica<\/p><\/blockquote>\n
<\/p>\n
2\u3001deepin V23<\/strong><\/h2>\nCurrently supports amd64 and arm64 architectures.<\/p>\n
sudo\u00a0apt\u00a0install\u00a0linglong-pica<\/p><\/blockquote>\n
<\/p>\n
10-Minute Quick Build<\/strong><\/h1>\nVisit the Linglong official website to obtain the 10-Minute Quick Build Guide\uff08https:\/\/linglong.dev\/<\/a>\uff09.<\/p>\n1\u3001Building an Example from Scratch<\/strong><\/h2>\nUse deepin-calculator<\/code> as an example to build a Linglong application from source code. The appid for a Linglong application should be named using a reversed domain name notation<\/p>\n1\uff09Create<\/strong><\/p>\nmkdir\u00a0org.deepin.calculator<\/p>\n
<\/p><\/blockquote>\n
Create a \"linglong.yaml file\"\u00a0 in the directory<\/p>\n
touch\u00a0org.deepin.calculator\/linglong.yaml<\/p>\n
<\/p><\/blockquote>\n
Enter the directory<\/p>\n
cd\u00a0org.deepin.calculator<\/p>\n
<\/p><\/blockquote>\n
Edit the linglong.yaml file using a text editor.<\/p>\n
![\"\"](\"https:\/\/storage.deepin.org\/thread\/202406060248063705_1.jpg\")
<\/p>\n
linglong.yaml file follows the YAML syntax specifications.<\/p>\n
<\/p>\n
2\uff09Build<\/strong><\/p>\nll-builder\u00a0build<\/p><\/blockquote>\n
Wait for the Linglong application to be built.<\/p>\n
<\/p>\n
3\uff09Run the Linglong application<\/strong><\/p>\nll-builder\u00a0run<\/p><\/blockquote>\n
If the ll-builder run command is successful, the output will be as follows:<\/p>\n
![\"\"](\"https:\/\/storage.deepin.org\/thread\/202406060249266604_2.jpg\")
<\/p>\n
<\/p>\n
For easier debugging, you can use the additional\u00a0 \"--exec \/bin\/bash\" parameter to replace the default program that is executed after entering the container, like this:<\/p>\n
ll-builder\u00a0run\u00a0--exec\u00a0\/bin\/bash<\/p><\/blockquote>\n
<\/p>\n
2\u3001Converting deb Applications<\/strong><\/h2>\nUsing Baidu Netdisk as an example, this section introduces the process of converting a deb package into a Linglong package. Currently, only software that adheres to the app store's packaging standards can be converted.<\/p>\n
1\uff09Obtain the deb package file<\/strong><\/p>\napt\u00a0download\u00a0com.baidu.baidunetdisk<\/p>\n
<\/p><\/blockquote>\n
2\uff09Convert the application<\/strong><\/p>\nll-pica\u00a0convert\u00a0-c\u00a0com.baidu.baidunetdisk_4.17.7_amd64.deb\u00a0-w\u00a0work\u00a0-b<\/p><\/blockquote>\n
Enter the directory<\/p>\n
cd\u00a0work\/package\/com.baidu.baidunetdisk\/amd64<\/p>\n
<\/p><\/blockquote>\n
3\uff09Install the layer file<\/strong><\/p>\nll-cli\u00a0install\u00a0.\/com.baidu.baidunetdisk_4.17.7.0_x86_64_runtime.layer<\/p>\n
<\/p><\/blockquote>\n
4\uff09Run the application<\/strong><\/p>\nll-cli run com.baidu.baidunetdisk<\/p><\/blockquote>\n
![\"\"](\"https:\/\/storage.deepin.org\/thread\/202406060250534425_3.jpg\")
<\/p>\n
<\/p>\n
Common Issues<\/strong><\/h1>\n1\u3001Common Build Issues<\/strong><\/h2>\n1)\u00a0 For cmake-based builds, if you encounter a failure with `-lxxxxx` but can find the library information with both `ldconfig` and `pkg-config`.<\/strong><\/p>\nThe library path is not in the standard path, and the new path is `\/runtime\/lib`.<\/p>\n
Add the environment variable `LIBRARY_PATH=<libpath>`. The current build environment already includes this environment variable by default.<\/p>\n
<\/p>\n
2\uff09Failure to link static libraries during build, requiring a rebuild with fPIC.<\/strong><\/p>\nUse the -fPIC parameter when building static libraries.<\/p>\n
<\/p>\n
3\uff09Failure to start the box during build, as shown in the figure below:<\/strong><\/p>\n![\"\"](\"https:\/\/storage.deepin.org\/thread\/202406060251038718_4.jpg\")
<\/p>\n
The kernel does not support unprivileged namespaces, solve this by enabling unprivileged namespaces.<\/p>\n
sudo\u00a0sysctl\u00a0-w\u00a0kernel.unprivileged_userns_clone=1<\/p><\/blockquote>\n
<\/p>\n
\n\n\n\n4) The qtbase build is successful, but it is not possible to build qt applications, with errors related to the module and mkspec.<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\nThere is an issue with the lower version of the fuse-overlay mount, which leads to file content corruption when qtbase is committed, making it unusable. Use a version of fuse-overlayfs that is >= 1.7.<\/p>\n
<\/p>\n
2\u3001Common Runtime Issues<\/strong><\/h2>\n1\uff09Why does the application fail to read the installation resource files under \/usr\/share when running?<\/strong><\/p>\nLinglong applications run in a container environment, and application data is mounted under \/opt\/apps\/<appid>\/. The \/usr\/share directory will only contain system data and will not contain application-related data. Therefore, reading directly from \/usr\/share will fail.<\/p>\n
Suggestion: Use the XDG_DATA_DIRS environment variable to read resources. The path \/opt\/apps\/<appid>\/files\/share will be included in the search path of this environment variable.<\/p>\n
<\/p>\n
2\uff09Why can't the application find the font library files when running? Why could they be read when the deb package was installed?<\/strong><\/p>\nWhen a deb package is installed, it brings along the corresponding font library files as dependencies. In contrast, the Linglong package format uses a self-contained packaging format.<\/p>\n
Apart from the basic system libraries and the Qt and DTK library files provided in the runtime, all other dependent data files must be provided by yourself.<\/p>\n
Suggestion: Place the corresponding data files in files\/share and use the environment variable XDG_DATA_DIRS to read the paths.<\/p>\n
<\/p>\n
3\uff09What is inside the Linglong application runtime? Can I add some library files to it?<\/strong><\/p>\nThe runtime that Linglong applications currently depend on provides Qt libraries and DTK libraries. Due to strict size limitations on the runtime, it is not currently allowed to add additional library files to the runtime.<\/p>\n
<\/p>\n
4\uff09Can configuration files be created at any path within the container during the application's runtime?<\/strong><\/p>\nConfiguration files can be created under `XDG_CONFIG_HOME`.<\/p>\n
<\/p>\n
5) Where is the application data saved? Where can it be found outside the container?<\/strong><\/p>\nBecause Linglong applications follow the principle of non-interference.<\/p>\n
The environment variables<\/p>\n
\n- XDG_DATA_HOME,<\/li>\n
- XDG_CONFIG_HOME,<\/li>\n
- XDG_CACHE_HOME<\/li>\n<\/ul>\n
are defined to point to the corresponding paths on the host machine at \"~\/.linglong\/<appid>\/.\" . Therefore, user application data is saved at this path. During the application's runtime, any data written should be done by reading and writing to the corresponding environment variables. It is forbidden to read from or write to the configurations of other applications.<\/p>\n
<\/p>\n
6\uff09How to place the provided D-Bus service file? What should be written in the Exec section?<\/strong><\/p>\nWhen an application provides a D-Bus service file, it needs to be placed in the `entries\/dbus-1\/services` directory. If the Exec section is to execute a binary within the Linglong package, use the `--exec` option parameter to execute the corresponding binary.<\/p>\n
<\/p>\n
7\uff09After the application is installed, the launcher cannot be found?<\/strong><\/p>\nIf `TryExec=xxx` is used and `xxx` is not found in the `$PATH`, the application will be considered non-existent and will not be displayed.<\/p>\n
<\/p>\n
8\uff09 Why does the icon appear as a small black dot?<\/strong><\/p>\nThe `.desktop` file has an `Icon` field specified, but the name of the icon field is incorrect or an absolute path is used.<\/p>\n
<\/p>\n
9\uff09Why does the icon appear as a gear?<\/strong><\/p>\nThe `.desktop` file does not provide an `Icon` field.<\/p>\n
<\/p>\n
10\uff09Where are the icons stored?<\/strong><\/p>\nFor SVG icons:<\/p>\n
svg\u00a0\u2192$PREFIX\/share\/icons\/hicolor\/scalable\/apps\/<\/p>\n
For other formats according to resolution, such as 16x16:<\/p>\n
png\/xpm\u00a0\u2192\u00a0$PREFIX\/share\/icons\/hicolor\/16X16\/apps\/<\/p>\n
<\/p>\n
11\uff09Why do the application's own xdg-open and xdg-email fail to work?<\/strong><\/p>\nIn the runtime, Linglong has special handling for xdg-open and xdg-email, so applications are prohibited from executing their own carried xdg-open and xdg-email executables or scripts.<\/p>\n
<\/p>\n
12\uff09Why are the system environment variables not effective when used by the application?<\/strong><\/p>\nWhen using environment variables, it is necessary to confirm whether the corresponding environment variables exist within the container. If they do not exist, you may need to contact the Linglong team for assistance.<\/p>\n
<\/p>\n
13\uff09How to provide missing library files required for application execution?<\/strong><\/p>\nThe application itself needs to provide the resource files and library files it requires. Place the library files in the $PREFIX\/lib directory.<\/p>\n
<\/p>\n
14\uff09Why does the Qt WebEngine rendering process crash during application runtime?<\/strong><\/p>\nThe system upgrade of glibc has caused the application to fail when using the built-in browser, requiring the application to be re-adapted.<\/p>\n
A temporary solution is to set the environment variable:<\/p>\n
export QTWEBENGINE_DISABLE_SANDBOX=1\u3002<\/p>\n
<\/p>\n
15\uff09Why can't the application find the\u00a0libqxcb.so\u00a0library or why does qtwebengine report an error?<\/strong><\/p>\nIf a qt.conf file exists, configure the correct path in the file, or use the following environment variables to configure the search paths:<\/p>\n
QTWEBENGINEPROCESS_PATH
\nQTWEBENGINE_RESOURCES_PATH
\nQT_QPA_PLATFORM_PLUGIN_PATH
\nQT_PLUGIN_PATH<\/p>\n
<\/p>\n
16\uff09Can the application carry its own database files and write data to the database during runtime?<\/strong><\/p>\nThe file system within the container is a read-only file system, and writing data to the application resource files is not allowed.<\/p>\n
<\/p>\n
17) Why does the execution of binaries with SUID or GUID permissions fail?<\/strong><\/p>\nTo ensure system security, Linglong containers prohibit the execution of binaries with such permissions.<\/p>\n
<\/p>\n
18) Why can't the input method in the uab offline package format be used on Debian or Ubuntu?<\/strong><\/p>\nIt is recommended to install the fictx input method and then try it out.<\/p>\n
<\/p>\n
19)\u00a0 How do you know which packages are installed in the container environment?<\/strong><\/p>\nUse ll-builder run --exec bash to enter the container environment, then use the command cat \/var\/lib\/dpkg\/status | grep \"^Package: \" to view the pre-installed software packages. Additionally, for libraries compiled from source, you can use cat \/runtime\/packages.list to view them.<\/p>\n
<\/p>\n
Scan the QR code below to join the Linglong community on WeChat:<\/strong><\/p>\n![\"\"](\"https:\/\/storage.deepin.org\/thread\/202406060253212540_5.jpg\")
<\/p>\n
<\/p>\n
\nAppendix:<\/strong><\/h1>\n1)\u00a0 \u00a0deepin V23 RC ISO : https:\/\/www.deepin.org\/en\/download\/<\/a><\/p>\n2)\u00a0 deepin Previous Versions: https:\/\/distrowatch.com\/table.php?distribution=deepin<\/p>\n
Content source: deepin community
\nReprinted with attribution<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"
Linglong As a new type of independent package management toolkit, Linglong primarily provides a layered and isolated operating environment, addressing compatibility issues caused by strong dependencies in traditional package management systems, as well as security issues resulting from lax permissions. Currently, Linglong supports four distributions, including deepin, UnionTech UOS, Debian, and Ubuntu. Linglong's isolation technology can completely decouple applications from the system, thereby thoroughly resolving compatibility conflicts between the system and applications, and among applications themselves, caused by upgrades and adaptation. For developers, this can effectively reduce development costs; for customers, it can reduce enterprise operational costs; and for the ...Read more<\/a><\/p>\n","protected":false},"author":11164,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[155,93],"tags":[],"_links":{"self":[{"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/posts\/33976"}],"collection":[{"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/users\/11164"}],"replies":[{"embeddable":true,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/comments?post=33976"}],"version-history":[{"count":13,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/posts\/33976\/revisions"}],"predecessor-version":[{"id":34003,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/posts\/33976\/revisions\/34003"}],"wp:attachment":[{"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/media?parent=33976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/categories?post=33976"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/tags?post=33976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Note: This document is applicable to version 1.5.0, please use\u00a0 \"ll-cli -- version\" \u00a0to check your Linglong program version.<\/p>\n<\/blockquote>\n
Linglong consists of three parts:<\/p>\n
- \n
- ll-builder is used for building and debugging Linglong applications, provided by linglong-builder;<\/li>\n
- ll-box is a sandbox container, provided by linglong-box;<\/li>\n
- ll-cli is for managing and running Linglong applications, provided by linglong-bin.<\/li>\n<\/ul>\n
<\/p>\n
1\u3001UOS 1070<\/strong><\/h2>\n
Currently supports amd64, arm64, and loongarch64 (Loongson old world) architectures.<\/p>\n
1)\u00a0 Add Linglong repository source<\/strong><\/p>\n
echo\u00a0\"deb [trusted=yes] https:\/\/ci.deepin.com\/repo\/deepin\/deepin-community\/linglong-repo\/ unstable main\"\u00a0|\u00a0sudo\u00a0tee\u00a0-a\u00a0\/etc\/apt\/sources.list<\/p><\/blockquote>\n
2) Install the Linglong build toolkit<\/strong><\/p>\n
sudo\u00a0apt\u00a0update<\/p>\n
sudo\u00a0apt\u00a0install\u00a0linglong-builder\u00a0linglong-box\u00a0linglong-bin<\/p><\/blockquote>\n
<\/p>\n
2\u3001deepin V23<\/strong><\/h2>\n
Currently supports amd64 and arm64 architectures.<\/p>\n
sudo\u00a0apt\u00a0install\u00a0linglong-builder\u00a0linglong-box\u00a0linglong-bin<\/p><\/blockquote>\n
<\/p>\n
Install the Pica Tool<\/strong><\/h1>\n
This tool currently offers the capability to convert deb packages into Linglong packages, generate the linglong.yaml file needed for building Linglong applications, and relies on ll-builder to implement application building and exportation.<\/p>\n
1\u3001UOS 1070<\/strong><\/h2>\n
Currently supports amd64 and arm64 architectures.<\/p>\n
According to the Linglong installation steps, add the Linglong repository source.<\/p>\n
sudo\u00a0apt\u00a0install\u00a0linglong-pica<\/p><\/blockquote>\n
<\/p>\n
2\u3001deepin V23<\/strong><\/h2>\n
Currently supports amd64 and arm64 architectures.<\/p>\n
sudo\u00a0apt\u00a0install\u00a0linglong-pica<\/p><\/blockquote>\n
<\/p>\n
10-Minute Quick Build<\/strong><\/h1>\n
Visit the Linglong official website to obtain the 10-Minute Quick Build Guide\uff08https:\/\/linglong.dev\/<\/a>\uff09.<\/p>\n
1\u3001Building an Example from Scratch<\/strong><\/h2>\n
Use
deepin-calculator<\/code> as an example to build a Linglong application from source code. The appid for a Linglong application should be named using a reversed domain name notation<\/p>\n1\uff09Create<\/strong><\/p>\n
mkdir\u00a0org.deepin.calculator<\/p>\n
<\/p><\/blockquote>\n
Create a \"linglong.yaml file\"\u00a0 in the directory<\/p>\n
touch\u00a0org.deepin.calculator\/linglong.yaml<\/p>\n
<\/p><\/blockquote>\n
Enter the directory<\/p>\n
cd\u00a0org.deepin.calculator<\/p>\n
<\/p><\/blockquote>\n
Edit the linglong.yaml file using a text editor.<\/p>\n
<\/p>\nlinglong.yaml file follows the YAML syntax specifications.<\/p>\n
<\/p>\n
2\uff09Build<\/strong><\/p>\n
ll-builder\u00a0build<\/p><\/blockquote>\n
Wait for the Linglong application to be built.<\/p>\n
<\/p>\n
3\uff09Run the Linglong application<\/strong><\/p>\n
ll-builder\u00a0run<\/p><\/blockquote>\n
If the ll-builder run command is successful, the output will be as follows:<\/p>\n
<\/p>\n<\/p>\n
For easier debugging, you can use the additional\u00a0 \"--exec \/bin\/bash\" parameter to replace the default program that is executed after entering the container, like this:<\/p>\n
ll-builder\u00a0run\u00a0--exec\u00a0\/bin\/bash<\/p><\/blockquote>\n
<\/p>\n
2\u3001Converting deb Applications<\/strong><\/h2>\n
Using Baidu Netdisk as an example, this section introduces the process of converting a deb package into a Linglong package. Currently, only software that adheres to the app store's packaging standards can be converted.<\/p>\n
1\uff09Obtain the deb package file<\/strong><\/p>\n
apt\u00a0download\u00a0com.baidu.baidunetdisk<\/p>\n
<\/p><\/blockquote>\n
2\uff09Convert the application<\/strong><\/p>\n
ll-pica\u00a0convert\u00a0-c\u00a0com.baidu.baidunetdisk_4.17.7_amd64.deb\u00a0-w\u00a0work\u00a0-b<\/p><\/blockquote>\n
Enter the directory<\/p>\n
cd\u00a0work\/package\/com.baidu.baidunetdisk\/amd64<\/p>\n
<\/p><\/blockquote>\n
3\uff09Install the layer file<\/strong><\/p>\n
ll-cli\u00a0install\u00a0.\/com.baidu.baidunetdisk_4.17.7.0_x86_64_runtime.layer<\/p>\n
<\/p><\/blockquote>\n
4\uff09Run the application<\/strong><\/p>\n
ll-cli run com.baidu.baidunetdisk<\/p><\/blockquote>\n
<\/p>\n<\/p>\n
Common Issues<\/strong><\/h1>\n
1\u3001Common Build Issues<\/strong><\/h2>\n
1)\u00a0 For cmake-based builds, if you encounter a failure with `-lxxxxx` but can find the library information with both `ldconfig` and `pkg-config`.<\/strong><\/p>\n
The library path is not in the standard path, and the new path is `\/runtime\/lib`.<\/p>\n
Add the environment variable `LIBRARY_PATH=<libpath>`. The current build environment already includes this environment variable by default.<\/p>\n
<\/p>\n
2\uff09Failure to link static libraries during build, requiring a rebuild with fPIC.<\/strong><\/p>\n
Use the -fPIC parameter when building static libraries.<\/p>\n
<\/p>\n
3\uff09Failure to start the box during build, as shown in the figure below:<\/strong><\/p>\n
<\/p>\nThe kernel does not support unprivileged namespaces, solve this by enabling unprivileged namespaces.<\/p>\n
sudo\u00a0sysctl\u00a0-w\u00a0kernel.unprivileged_userns_clone=1<\/p><\/blockquote>\n
<\/p>\n
\n\n\n\n4) The qtbase build is successful, but it is not possible to build qt applications, with errors related to the module and mkspec.<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
There is an issue with the lower version of the fuse-overlay mount, which leads to file content corruption when qtbase is committed, making it unusable. Use a version of fuse-overlayfs that is >= 1.7.<\/p>\n
<\/p>\n
2\u3001Common Runtime Issues<\/strong><\/h2>\n
1\uff09Why does the application fail to read the installation resource files under \/usr\/share when running?<\/strong><\/p>\n
Linglong applications run in a container environment, and application data is mounted under \/opt\/apps\/<appid>\/. The \/usr\/share directory will only contain system data and will not contain application-related data. Therefore, reading directly from \/usr\/share will fail.<\/p>\n
Suggestion: Use the XDG_DATA_DIRS environment variable to read resources. The path \/opt\/apps\/<appid>\/files\/share will be included in the search path of this environment variable.<\/p>\n
<\/p>\n
2\uff09Why can't the application find the font library files when running? Why could they be read when the deb package was installed?<\/strong><\/p>\n
When a deb package is installed, it brings along the corresponding font library files as dependencies. In contrast, the Linglong package format uses a self-contained packaging format.<\/p>\n
Apart from the basic system libraries and the Qt and DTK library files provided in the runtime, all other dependent data files must be provided by yourself.<\/p>\n
Suggestion: Place the corresponding data files in files\/share and use the environment variable XDG_DATA_DIRS to read the paths.<\/p>\n
<\/p>\n
3\uff09What is inside the Linglong application runtime? Can I add some library files to it?<\/strong><\/p>\n
The runtime that Linglong applications currently depend on provides Qt libraries and DTK libraries. Due to strict size limitations on the runtime, it is not currently allowed to add additional library files to the runtime.<\/p>\n
<\/p>\n
4\uff09Can configuration files be created at any path within the container during the application's runtime?<\/strong><\/p>\n
Configuration files can be created under `XDG_CONFIG_HOME`.<\/p>\n
<\/p>\n
5) Where is the application data saved? Where can it be found outside the container?<\/strong><\/p>\n
Because Linglong applications follow the principle of non-interference.<\/p>\n
The environment variables<\/p>\n
- \n
- XDG_DATA_HOME,<\/li>\n
- XDG_CONFIG_HOME,<\/li>\n
- XDG_CACHE_HOME<\/li>\n<\/ul>\n
are defined to point to the corresponding paths on the host machine at \"~\/.linglong\/<appid>\/.\" . Therefore, user application data is saved at this path. During the application's runtime, any data written should be done by reading and writing to the corresponding environment variables. It is forbidden to read from or write to the configurations of other applications.<\/p>\n
<\/p>\n
6\uff09How to place the provided D-Bus service file? What should be written in the Exec section?<\/strong><\/p>\n
When an application provides a D-Bus service file, it needs to be placed in the `entries\/dbus-1\/services` directory. If the Exec section is to execute a binary within the Linglong package, use the `--exec` option parameter to execute the corresponding binary.<\/p>\n
<\/p>\n
7\uff09After the application is installed, the launcher cannot be found?<\/strong><\/p>\n
If `TryExec=xxx` is used and `xxx` is not found in the `$PATH`, the application will be considered non-existent and will not be displayed.<\/p>\n
<\/p>\n
8\uff09 Why does the icon appear as a small black dot?<\/strong><\/p>\n
The `.desktop` file has an `Icon` field specified, but the name of the icon field is incorrect or an absolute path is used.<\/p>\n
<\/p>\n
9\uff09Why does the icon appear as a gear?<\/strong><\/p>\n
The `.desktop` file does not provide an `Icon` field.<\/p>\n
<\/p>\n
10\uff09Where are the icons stored?<\/strong><\/p>\n
For SVG icons:<\/p>\n
svg\u00a0\u2192$PREFIX\/share\/icons\/hicolor\/scalable\/apps\/<\/p>\n
For other formats according to resolution, such as 16x16:<\/p>\n
png\/xpm\u00a0\u2192\u00a0$PREFIX\/share\/icons\/hicolor\/16X16\/apps\/<\/p>\n
<\/p>\n
11\uff09Why do the application's own xdg-open and xdg-email fail to work?<\/strong><\/p>\n
In the runtime, Linglong has special handling for xdg-open and xdg-email, so applications are prohibited from executing their own carried xdg-open and xdg-email executables or scripts.<\/p>\n
<\/p>\n
12\uff09Why are the system environment variables not effective when used by the application?<\/strong><\/p>\n
When using environment variables, it is necessary to confirm whether the corresponding environment variables exist within the container. If they do not exist, you may need to contact the Linglong team for assistance.<\/p>\n
<\/p>\n
13\uff09How to provide missing library files required for application execution?<\/strong><\/p>\n
The application itself needs to provide the resource files and library files it requires. Place the library files in the $PREFIX\/lib directory.<\/p>\n
<\/p>\n
14\uff09Why does the Qt WebEngine rendering process crash during application runtime?<\/strong><\/p>\n
The system upgrade of glibc has caused the application to fail when using the built-in browser, requiring the application to be re-adapted.<\/p>\n
A temporary solution is to set the environment variable:<\/p>\n
export QTWEBENGINE_DISABLE_SANDBOX=1\u3002<\/p>\n
<\/p>\n
15\uff09Why can't the application find the\u00a0libqxcb.so\u00a0library or why does qtwebengine report an error?<\/strong><\/p>\n
If a qt.conf file exists, configure the correct path in the file, or use the following environment variables to configure the search paths:<\/p>\n
QTWEBENGINEPROCESS_PATH
\nQTWEBENGINE_RESOURCES_PATH
\nQT_QPA_PLATFORM_PLUGIN_PATH
\nQT_PLUGIN_PATH<\/p>\n<\/p>\n
16\uff09Can the application carry its own database files and write data to the database during runtime?<\/strong><\/p>\n
The file system within the container is a read-only file system, and writing data to the application resource files is not allowed.<\/p>\n
<\/p>\n
17) Why does the execution of binaries with SUID or GUID permissions fail?<\/strong><\/p>\n
To ensure system security, Linglong containers prohibit the execution of binaries with such permissions.<\/p>\n
<\/p>\n
18) Why can't the input method in the uab offline package format be used on Debian or Ubuntu?<\/strong><\/p>\n
It is recommended to install the fictx input method and then try it out.<\/p>\n
<\/p>\n
19)\u00a0 How do you know which packages are installed in the container environment?<\/strong><\/p>\n
Use ll-builder run --exec bash to enter the container environment, then use the command cat \/var\/lib\/dpkg\/status | grep \"^Package: \" to view the pre-installed software packages. Additionally, for libraries compiled from source, you can use cat \/runtime\/packages.list to view them.<\/p>\n
<\/p>\n
Scan the QR code below to join the Linglong community on WeChat:<\/strong><\/p>\n
<\/p>\n<\/p>\n
\nAppendix:<\/strong><\/h1>\n
1)\u00a0 \u00a0deepin V23 RC ISO : https:\/\/www.deepin.org\/en\/download\/<\/a><\/p>\n
2)\u00a0 deepin Previous Versions: https:\/\/distrowatch.com\/table.php?distribution=deepin<\/p>\n
Content source: deepin community
\nReprinted with attribution<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"Linglong As a new type of independent package management toolkit, Linglong primarily provides a layered and isolated operating environment, addressing compatibility issues caused by strong dependencies in traditional package management systems, as well as security issues resulting from lax permissions. Currently, Linglong supports four distributions, including deepin, UnionTech UOS, Debian, and Ubuntu. Linglong's isolation technology can completely decouple applications from the system, thereby thoroughly resolving compatibility conflicts between the system and applications, and among applications themselves, caused by upgrades and adaptation. For developers, this can effectively reduce development costs; for customers, it can reduce enterprise operational costs; and for the ...Read more<\/a><\/p>\n","protected":false},"author":11164,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[155,93],"tags":[],"_links":{"self":[{"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/posts\/33976"}],"collection":[{"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/users\/11164"}],"replies":[{"embeddable":true,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/comments?post=33976"}],"version-history":[{"count":13,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/posts\/33976\/revisions"}],"predecessor-version":[{"id":34003,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/posts\/33976\/revisions\/34003"}],"wp:attachment":[{"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/media?parent=33976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/categories?post=33976"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.deepin.org.cn\/en\/wp-json\/wp\/v2\/tags?post=33976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}