diff --git a/Tools/Sailfish_SDK/Installation/README.md b/Tools/Sailfish_SDK/Installation/README.md index bc94a844..9a640928 100644 --- a/Tools/Sailfish_SDK/Installation/README.md +++ b/Tools/Sailfish_SDK/Installation/README.md @@ -61,12 +61,6 @@ You may also consider configuring MSYS2 to use your Windows user home directory. db_home: windows cygwin desc -When Docker is used, ensure that the `docker` command line tool is available on `PATH` under the MSYS2 shell. This can be accomplished by adding, e.g., - - export PATH="$PATH:/c/Program Files/Docker/Docker/resources/bin/" - -to the `~/.bash_profile` script under the MSYS2 shell and reopening the shell. - ### System Requirements - About 15GB of free disk space for the default component selection - When Docker is used, installed files are split between the Sailfish SDK installation directory and Docker's [data-root](https://docs.docker.com/config/daemon/#docker-daemon-directory). Ensure that both provide enough free space. diff --git a/Tools/Sailfish_SDK/Known_Issues/README.md b/Tools/Sailfish_SDK/Known_Issues/README.md index c2e08862..3e702fc6 100644 --- a/Tools/Sailfish_SDK/Known_Issues/README.md +++ b/Tools/Sailfish_SDK/Known_Issues/README.md @@ -55,14 +55,6 @@ These are the known issues with the Sailfish SDK. If you have any questions, fee - Sailfish IDE needs restart after changing SSH port of a Docker based build engine - Error starting the build engine on [Linux hosts with cgroups v2](https://forum.sailfishos.org/t/issues-with-installing-sailfish-sdk-docker-with-debian-bullseye-11/4454) - It is usually possible to revert back to cgroups v1 by adding `systemd.unified_cgroup_hierarchy=false` to the host kernel command line - - On some systems package manager gets stuck or crashes due to unreasonably high file descriptor limit and builds will not get past initialization phase. You may stop build engine with `sfdk engine stop` and then use this workaround: - - sfdk engine exec sudo tee /etc/security/limits.d/95-nofile-sdk-fix.conf <