Problem Description
A fresh deployment of Debian Bookworm via Linux Deploy fails during the configuration stage, leaving core dependencies broken. However, a step-by-step upgrade from Bullseye works perfectly.
Additionally, on Android 15, strict kernel socket restrictions completely block network access unless the user UID is modified.
1. Debian Bookworm Bootstrap Dependency Issue
When attempting a direct installation of Debian Bookworm, the deployment fails near the end during the SSH setup phase, leaving openssh-server and usrmerge in an unconfigured state due to unsatisfied dependencies (perl:any):
I seguenti pacchetti hanno dipendenze non soddisfatte:
libfile-find-rule-perl : Dipende: perl:any
openssh-server : Dipende: openssh-client (= 1:9.2p1-2+deb12u7) ma non sta per essere installato
...
usrmerge : Dipende: perl:any
The Working Solution:
To successfully get a working Bookworm environment, the user must:
- Set the profile suite to
bullseye editing directly the /data/data/ru.meefik.linuxdeploy/files/config/linux.conf and run the fresh installation (which completes successfully without dependency blocks).
- Once Bullseye is deployed, execute a manual
apt update && apt dist-upgrade to safely upgrade the container to Bookworm. This path works flawlessly because the core environment is already correctly structured by the previous Debian 11 base.
2. Android 15 Socket Restriction (SSH/Network Fix)
Once upgraded or deployed on Android 15, the container suffers from strict host kernel-level socket restrictions that block network allocation for high user IDs. This is why many users are reporting that the SSH daemon fails to start or accept connections.
The Proven Fix:
To restore full socket and network capabilities for SSH and other services on Android 15, the container user UID must be changed. Changing the default UID down from 60000 to 6000 with usermod and groupmod completely bypasses the Android 15 network socket block, restoring perfect connectivity.
Problem Description
A fresh deployment of Debian Bookworm via Linux Deploy fails during the configuration stage, leaving core dependencies broken. However, a step-by-step upgrade from Bullseye works perfectly.
Additionally, on Android 15, strict kernel socket restrictions completely block network access unless the user UID is modified.
1. Debian Bookworm Bootstrap Dependency Issue
When attempting a direct installation of Debian Bookworm, the deployment fails near the end during the SSH setup phase, leaving
openssh-serverandusrmergein an unconfigured state due to unsatisfied dependencies (perl:any):The Working Solution:
To successfully get a working Bookworm environment, the user must:
bullseyeediting directly the /data/data/ru.meefik.linuxdeploy/files/config/linux.conf and run the fresh installation (which completes successfully without dependency blocks).apt update && apt dist-upgradeto safely upgrade the container to Bookworm. This path works flawlessly because the core environment is already correctly structured by the previous Debian 11 base.2. Android 15 Socket Restriction (SSH/Network Fix)
Once upgraded or deployed on Android 15, the container suffers from strict host kernel-level socket restrictions that block network allocation for high user IDs. This is why many users are reporting that the SSH daemon fails to start or accept connections.
The Proven Fix:
To restore full socket and network capabilities for SSH and other services on Android 15, the container user UID must be changed. Changing the default UID down from
60000to6000with usermod and groupmod completely bypasses the Android 15 network socket block, restoring perfect connectivity.