Discussion:
Bug#930198: Please have it make sure it doesn't use existing users
Add Reply
積丹尼 Dan Jacobson
2019-06-08 01:50:01 UTC
Reply
Permalink
Package: anbox
Version: 0.0~git20190124-1
Severity: minor

All I know is I did

# systemctl start anbox-container-manager.service
$ anbox session-manager& #as user 1000
$ ps auxn|grep android
10020 8924 0.1 2.9 1143792 176188 pts/2 Sl 09:22 0:01 com.android.systemui
1001 8981 0.0 1.7 1039296 106880 pts/2 Sl 09:22 0:00 com.android.phone
1000 8995 0.0 1.5 1051476 95020 pts/2 Sl 09:22 0:00 com.android.settings:CryptKeeper
1000 9026 0.0 1.7 1059708 102228 pts/2 Sl 09:22 0:00 com.android.settings
10009 9110 0.0 1.2 1014364 73260 pts/2 Sl 09:22 0:00 android.ext.services
10032 9125 0.0 1.4 1027264 89140 pts/2 Sl 09:22 0:00 com.android.deskclock
10015 9140 0.0 1.4 1016188 87260 pts/2 Sl 09:22 0:00 com.android.provision
10047 9149 0.0 1.2 1013392 73500 pts/2 Sl 09:22 0:00 com.android.smspush ...

The problems is that 1000 and 1001 are already existing users on the
system.

In fact 1001 is a totally unrelated user.

Please have it make sure it doesn't use existing users.
Shengjing Zhu
2019-07-21 22:10:02 UTC
Reply
Permalink
Post by 積丹尼 Dan Jacobson
Package: anbox
Version: 0.0~git20190124-1
Severity: minor
All I know is I did
# systemctl start anbox-container-manager.service
$ anbox session-manager& #as user 1000
$ ps auxn|grep android
10020 8924 0.1 2.9 1143792 176188 pts/2 Sl 09:22 0:01 com.android.systemui
1001 8981 0.0 1.7 1039296 106880 pts/2 Sl 09:22 0:00 com.android.phone
1000 8995 0.0 1.5 1051476 95020 pts/2 Sl 09:22 0:00 com.android.settings:CryptKeeper
1000 9026 0.0 1.7 1059708 102228 pts/2 Sl 09:22 0:00 com.android.settings
10009 9110 0.0 1.2 1014364 73260 pts/2 Sl 09:22 0:00 android.ext.services
10032 9125 0.0 1.4 1027264 89140 pts/2 Sl 09:22 0:00 com.android.deskclock
10015 9140 0.0 1.4 1016188 87260 pts/2 Sl 09:22 0:00 com.android.provision
10047 9149 0.0 1.2 1013392 73500 pts/2 Sl 09:22 0:00 com.android.smspush ...
The problems is that 1000 and 1001 are already existing users on the
system.
In fact 1001 is a totally unrelated user.
Please have it make sure it doesn't use existing users.
This is how lxc or other containers(like docker) work. The user 1001
is in lxc, but when you show process info outside the lxc, you will
see the confused result.

Though there's some way to fix it, using the unprivileged mode. This
involves complicated steps, but you can try. First learn how to setup
subuid/subgid for lxc, then edit the anbox-container-manager.service
and remove the --privileged argument.
--
Shengjing Zhu
積丹尼 Dan Jacobson
2019-07-22 12:30:02 UTC
Reply
Permalink
Why doesn't whatever is translating / picking user numbers just start at
1100 or even 1050?

All linux systems will have a 1000 conflict. And many might have a 1001
conflict.

But when you get to 1050 I bet there are only e.g., Dreamhost shared
servers, that probably won't be running anbox!

Loading...