Problem with anbox container on ARM64
When I run anbox session-manager command (not root) I get this error:
dbus[19950]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
[ 2019-01-23 13:04:51] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to set config item lxc.pts
[ 2019-01-23 13:04:51] [session_manager.cpp:145@operator()] Lost connection to container manager, terminating.
[ 2019-01-23 13:04:52] [daemon.cpp:61@Run] Container is not running
[ 2019-01-23 13:04:52] [session_manager.cpp:145@operator()] Lost connection to container manager, terminating.
Stack trace (most recent call last) in thread 19961.
Also, when I run anbox launch, I get this:
switch@switch:~$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
dbus[26097]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
[ 2019-01-23 13:09:54] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
Also I have to say, that when running an anbox window pops up (starting...) and then close when appearing:
[ 2019-01-23 13:09:54] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
Could this be a problem when I use an old android image version of anbox for arm64?
I used this image to setup the container:
https://build.anbox.io/android-images/2017/08/04/
Greetings!
PS: here's the container's config:
lxc.mount.auto = proc:mixed sys:mixed cgroup:mixed
lxc.autodev = 1
lxc.pty.max = 1024
lxc.tty.max = 0
lxc.uts.name = anbox
lxc.environment = PATH=/system/bin:/system/sbin:/system/xbin
lxc.init.cmd = /anbox-init.sh
lxc.rootfs.path = /var/lib/anbox/rootfs
lxc.log.level = 0
lxc.log.file = /var/lib/anbox/logs/container.log
lxc.console.logfile = /var/lib/anbox/logs/console.log
lxc.console.rotate = 1
lxc.apparmor.profile = unconfined
lxc.idmap = u 0 100000 999
lxc.idmap = g 0 100000 999
lxc.idmap = u 1000 1000 1
lxc.idmap = g 1000 1000 1
lxc.idmap = u 1001 101001 64535
lxc.idmap = g 1001 101001 64535
lxc.mount.entry = /run/user/1000/anbox/sockets/qemu_pipe /var/lib/anbox/rootfs/dev/qemu_pipe none bind,create=file,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/sockets/anbox_audio /var/lib/anbox/rootfs/dev/anbox_audio none bind,create=file,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/input /var/lib/anbox/rootfs/dev/input none bind,create=dir,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/sockets/anbox_bridge /var/lib/anbox/rootfs/dev/anbox_bridge none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/zero dev/zero none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/urandom dev/urandom none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/random dev/random none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/ashmem dev/ashmem none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/fuse dev/fuse none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/binder dev/binder none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/console dev/console none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/full dev/full none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/tty dev/tty none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/state/default.prop /var/lib/anbox/rootfs/default.prop none bind,optional,ro 0 0
lxc
add a comment |
When I run anbox session-manager command (not root) I get this error:
dbus[19950]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
[ 2019-01-23 13:04:51] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to set config item lxc.pts
[ 2019-01-23 13:04:51] [session_manager.cpp:145@operator()] Lost connection to container manager, terminating.
[ 2019-01-23 13:04:52] [daemon.cpp:61@Run] Container is not running
[ 2019-01-23 13:04:52] [session_manager.cpp:145@operator()] Lost connection to container manager, terminating.
Stack trace (most recent call last) in thread 19961.
Also, when I run anbox launch, I get this:
switch@switch:~$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
dbus[26097]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
[ 2019-01-23 13:09:54] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
Also I have to say, that when running an anbox window pops up (starting...) and then close when appearing:
[ 2019-01-23 13:09:54] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
Could this be a problem when I use an old android image version of anbox for arm64?
I used this image to setup the container:
https://build.anbox.io/android-images/2017/08/04/
Greetings!
PS: here's the container's config:
lxc.mount.auto = proc:mixed sys:mixed cgroup:mixed
lxc.autodev = 1
lxc.pty.max = 1024
lxc.tty.max = 0
lxc.uts.name = anbox
lxc.environment = PATH=/system/bin:/system/sbin:/system/xbin
lxc.init.cmd = /anbox-init.sh
lxc.rootfs.path = /var/lib/anbox/rootfs
lxc.log.level = 0
lxc.log.file = /var/lib/anbox/logs/container.log
lxc.console.logfile = /var/lib/anbox/logs/console.log
lxc.console.rotate = 1
lxc.apparmor.profile = unconfined
lxc.idmap = u 0 100000 999
lxc.idmap = g 0 100000 999
lxc.idmap = u 1000 1000 1
lxc.idmap = g 1000 1000 1
lxc.idmap = u 1001 101001 64535
lxc.idmap = g 1001 101001 64535
lxc.mount.entry = /run/user/1000/anbox/sockets/qemu_pipe /var/lib/anbox/rootfs/dev/qemu_pipe none bind,create=file,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/sockets/anbox_audio /var/lib/anbox/rootfs/dev/anbox_audio none bind,create=file,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/input /var/lib/anbox/rootfs/dev/input none bind,create=dir,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/sockets/anbox_bridge /var/lib/anbox/rootfs/dev/anbox_bridge none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/zero dev/zero none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/urandom dev/urandom none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/random dev/random none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/ashmem dev/ashmem none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/fuse dev/fuse none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/binder dev/binder none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/console dev/console none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/full dev/full none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/tty dev/tty none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/state/default.prop /var/lib/anbox/rootfs/default.prop none bind,optional,ro 0 0
lxc
add a comment |
When I run anbox session-manager command (not root) I get this error:
dbus[19950]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
[ 2019-01-23 13:04:51] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to set config item lxc.pts
[ 2019-01-23 13:04:51] [session_manager.cpp:145@operator()] Lost connection to container manager, terminating.
[ 2019-01-23 13:04:52] [daemon.cpp:61@Run] Container is not running
[ 2019-01-23 13:04:52] [session_manager.cpp:145@operator()] Lost connection to container manager, terminating.
Stack trace (most recent call last) in thread 19961.
Also, when I run anbox launch, I get this:
switch@switch:~$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
dbus[26097]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
[ 2019-01-23 13:09:54] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
Also I have to say, that when running an anbox window pops up (starting...) and then close when appearing:
[ 2019-01-23 13:09:54] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
Could this be a problem when I use an old android image version of anbox for arm64?
I used this image to setup the container:
https://build.anbox.io/android-images/2017/08/04/
Greetings!
PS: here's the container's config:
lxc.mount.auto = proc:mixed sys:mixed cgroup:mixed
lxc.autodev = 1
lxc.pty.max = 1024
lxc.tty.max = 0
lxc.uts.name = anbox
lxc.environment = PATH=/system/bin:/system/sbin:/system/xbin
lxc.init.cmd = /anbox-init.sh
lxc.rootfs.path = /var/lib/anbox/rootfs
lxc.log.level = 0
lxc.log.file = /var/lib/anbox/logs/container.log
lxc.console.logfile = /var/lib/anbox/logs/console.log
lxc.console.rotate = 1
lxc.apparmor.profile = unconfined
lxc.idmap = u 0 100000 999
lxc.idmap = g 0 100000 999
lxc.idmap = u 1000 1000 1
lxc.idmap = g 1000 1000 1
lxc.idmap = u 1001 101001 64535
lxc.idmap = g 1001 101001 64535
lxc.mount.entry = /run/user/1000/anbox/sockets/qemu_pipe /var/lib/anbox/rootfs/dev/qemu_pipe none bind,create=file,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/sockets/anbox_audio /var/lib/anbox/rootfs/dev/anbox_audio none bind,create=file,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/input /var/lib/anbox/rootfs/dev/input none bind,create=dir,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/sockets/anbox_bridge /var/lib/anbox/rootfs/dev/anbox_bridge none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/zero dev/zero none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/urandom dev/urandom none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/random dev/random none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/ashmem dev/ashmem none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/fuse dev/fuse none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/binder dev/binder none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/console dev/console none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/full dev/full none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/tty dev/tty none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/state/default.prop /var/lib/anbox/rootfs/default.prop none bind,optional,ro 0 0
lxc
When I run anbox session-manager command (not root) I get this error:
dbus[19950]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
[ 2019-01-23 13:04:51] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to set config item lxc.pts
[ 2019-01-23 13:04:51] [session_manager.cpp:145@operator()] Lost connection to container manager, terminating.
[ 2019-01-23 13:04:52] [daemon.cpp:61@Run] Container is not running
[ 2019-01-23 13:04:52] [session_manager.cpp:145@operator()] Lost connection to container manager, terminating.
Stack trace (most recent call last) in thread 19961.
Also, when I run anbox launch, I get this:
switch@switch:~$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
dbus[26097]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
[ 2019-01-23 13:09:54] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
Also I have to say, that when running an anbox window pops up (starting...) and then close when appearing:
[ 2019-01-23 13:09:54] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
Could this be a problem when I use an old android image version of anbox for arm64?
I used this image to setup the container:
https://build.anbox.io/android-images/2017/08/04/
Greetings!
PS: here's the container's config:
lxc.mount.auto = proc:mixed sys:mixed cgroup:mixed
lxc.autodev = 1
lxc.pty.max = 1024
lxc.tty.max = 0
lxc.uts.name = anbox
lxc.environment = PATH=/system/bin:/system/sbin:/system/xbin
lxc.init.cmd = /anbox-init.sh
lxc.rootfs.path = /var/lib/anbox/rootfs
lxc.log.level = 0
lxc.log.file = /var/lib/anbox/logs/container.log
lxc.console.logfile = /var/lib/anbox/logs/console.log
lxc.console.rotate = 1
lxc.apparmor.profile = unconfined
lxc.idmap = u 0 100000 999
lxc.idmap = g 0 100000 999
lxc.idmap = u 1000 1000 1
lxc.idmap = g 1000 1000 1
lxc.idmap = u 1001 101001 64535
lxc.idmap = g 1001 101001 64535
lxc.mount.entry = /run/user/1000/anbox/sockets/qemu_pipe /var/lib/anbox/rootfs/dev/qemu_pipe none bind,create=file,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/sockets/anbox_audio /var/lib/anbox/rootfs/dev/anbox_audio none bind,create=file,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/input /var/lib/anbox/rootfs/dev/input none bind,create=dir,optional 0 0
lxc.mount.entry = /run/user/1000/anbox/sockets/anbox_bridge /var/lib/anbox/rootfs/dev/anbox_bridge none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/zero dev/zero none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/urandom dev/urandom none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/random dev/random none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/ashmem dev/ashmem none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/fuse dev/fuse none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/binder dev/binder none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/console dev/console none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/full dev/full none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/devices/tty dev/tty none bind,create=file,optional 0 0
lxc.mount.entry = /var/lib/anbox/state/default.prop /var/lib/anbox/rootfs/default.prop none bind,optional,ro 0 0
lxc
lxc
edited Feb 5 at 19:26
Android Dev
11k63362
11k63362
asked Feb 5 at 19:25
Pato SublimeArmyPato SublimeArmy
11
11
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115900%2fproblem-with-anbox-container-on-arm64%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115900%2fproblem-with-anbox-container-on-arm64%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown