Failed to configure LXC container with lxc 3.0 #669
Comments
i have the same problem under the newest arch linux. |
anbox.sh:
anbox.service:
I don't actually remember exactly what I was doing with the service, but this is the general direction you need to go to solve this issue. At least, I think it is. I ran into the generic "waited too long, something has gone wrong" error after doing this stuff. For some reason I later uninstalled it, and now can't install again (#637), so I can't verify or test any of this. ED: #236 (comment) was heavily related to how I came up with the above. |
The same issue. |
@zergling-man As far as I can see the only thing I can see you are doing that is different is running with the session-manager with |
I'm trying to debug this. I've started by making a patch to show which
With this I get this error:
Right. So I checked out the lxc documention. So unless anbox supports lxc < 2.1, we can fix this by using However, according to I tried doing this, and just got a different error, which I'm yet to investigate. But I think a workaround for arch users in the mean time is to maybe downgrade |
@Bertil-100 Please will you change the title of the bug to |
I was able to get anbox running with lxc 3.0 with this patch
I would like to submit a pull request. @morphis Please can I get feed back which of the following options you would prefer:
|
@garyvdm according to the lxc documentation, lxc.network should be changed to lxc.net.0 |
This patch does not work for me. I'm still getting the same error. |
@garyvdm I apply your patch on Archlinux, based on anbox-git.It seems to work. It no longer generate an error when I execute the command, and some process are running . I also can find device in adb. But I when i execute |
The same for me.. it hangs in boot looping :( |
@garyvdm The plan is to switch to LXC 3.x real soon when we migrate the snap to a 18.04 base as well. So I am happy to receive a PR doing the legwork for this and will merge it as soon as we're at that point. How does that sound? |
Ok - I will submit a PR tonight.
…On Mon, May 21, 2018 at 8:36 PM, Simon Fels ***@***.***> wrote:
@garyvdm <https://github.com/garyvdm> The plan is to switch to LXC 3.x
real soon when we migrate the snap to a 18.04 base as well. So I am happy
to receive a PR doing the legwork for this and will merge it as soon as
we're at that point. How does that sound?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#669 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAVfr-3hNFjKhsqubefor0XtWgDiR8Ezks5t0wk2gaJpZM4TEvu3>
.
|
Thanks to @garyvdm spotting and debugging the issue first. It's better, however, not to drop the The below alternative approach clears the way to see an already reported error: The whole thing (patching
|
@mprogram You made a typo with the file name on one line. This seems to be correct:
It's not working for me on Arch though. Still getting the same error.
|
@Tanner-Lin, thanks for edits, indeed one typo near the end instead of
It must work on Arch as I ported pacman to a bleeding edge Debian-system and succesfully cross-compiled it to run it there. On my computer I only pay attention to defferences You may want to merge @morphis' changes from his fork/branch of latest unmerged commits manually to advance anbox's code a little bit further. Additionally don't forget to switch usr.bin.lxc AppArmor profile into complain mode with Let's concentrate on why it doesn't start with |
Update: I have successfully compiled and also started the latest code, double-checked with |
can be closed then? |
Surely. |
** Please paste the result of
anbox system-info
below:**anbox system-info
version: local-03f69c8
os:
name: Antergos Linux
version: 18.3-ISO-Rolling
snap-based: false
kernel:
version: Linux version 4.15.14-1-ARCH (builduser@heftig-6127) (gcc version 7.3.1 20180312 (GCC)) #1 SMP PREEMPT Wed Mar 28 17:34:29 UTC 2018
binder: true
ashmem: true
graphics:
egl:
vendor: Mesa Project
version: 1.4 (DRI2)
extensions:
- EGL_ANDROID_native_fence_sync
- EGL_CHROMIUM_sync_control
- EGL_EXT_buffer_age
- EGL_EXT_create_context_robustness
- EGL_EXT_image_dma_buf_import
- EGL_EXT_image_dma_buf_import_modifiers
- EGL_IMG_context_priority
- EGL_KHR_config_attribs
- EGL_KHR_create_context
- EGL_KHR_create_context_no_error
- EGL_KHR_fence_sync
- EGL_KHR_get_all_proc_addresses
- EGL_KHR_gl_renderbuffer_image
- EGL_KHR_gl_texture_2D_image
- EGL_KHR_gl_texture_3D_image
- EGL_KHR_gl_texture_cubemap_image
- EGL_KHR_image
- EGL_KHR_image_base
- EGL_KHR_image_pixmap
- EGL_KHR_no_config_context
- EGL_KHR_reusable_sync
- EGL_KHR_surfaceless_context
- EGL_KHR_wait_sync
- EGL_MESA_configless_context
- EGL_MESA_drm_image
- EGL_MESA_image_dma_buf_export
- EGL_NOK_texture_from_pixmap
- EGL_WL_bind_wayland_display
gles2:
vendor: Intel Open Source Technology Center
vendor: OpenGL ES-CM 1.1 Mesa 17.3.7
extensions:
- GL_EXT_blend_minmax
- GL_EXT_multi_draw_arrays
- GL_EXT_texture_filter_anisotropic
- GL_EXT_texture_lod_bias
- GL_OES_byte_coordinates
- GL_OES_fixed_point
- GL_OES_stencil_wrap
- GL_OES_compressed_paletted_texture
- GL_OES_query_matrix
- GL_OES_read_format
- GL_OES_single_precision
- GL_EXT_texture_compression_dxt1
- GL_OES_draw_texture
- GL_OES_point_size_array
- GL_OES_point_sprite
- GL_EXT_texture_format_BGRA8888
- GL_OES_compressed_ETC1_RGB8_texture
- GL_OES_depth24
- GL_OES_element_index_uint
- GL_OES_fbo_render_mipmap
- GL_OES_framebuffer_object
- GL_OES_mapbuffer
- GL_OES_rgb8_rgba8
- GL_OES_stencil8
- GL_OES_texture_env_crossbar
- GL_OES_texture_mirrored_repeat
- GL_OES_texture_npot
- GL_OES_EGL_image
- GL_OES_packed_depth_stencil
- GL_OES_texture_cube_map
- GL_APPLE_texture_max_level
- GL_EXT_discard_framebuffer
- GL_EXT_read_format_bgra
- GL_OES_blend_equation_separate
- GL_OES_blend_func_separate
- GL_OES_blend_subtract
- GL_OES_EGL_image_external
- GL_OES_EGL_sync
- GL_OES_vertex_array_object
- GL_ANGLE_texture_compression_dxt3
- GL_ANGLE_texture_compression_dxt5
- GL_EXT_map_buffer_range
- GL_KHR_debug
- GL_OES_required_internalformat
- GL_OES_surfaceless_context
- GL_EXT_compressed_ETC1_RGB8_sub_texture
- GL_EXT_polygon_offset_clamp
- GL_KHR_no_error
Please describe your problem:
$ anbox session-manager
[ 2018-04-03 09:21:43] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to configure LXC container
[ 2018-04-03 09:21:43] [session_manager.cpp:162@operator()] Lost connection to container manager, terminating.
[ 2018-04-03 09:21:43] [daemon.cpp:58@Run] Container is not running
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorboost::log::v2_mt_posix::system_error >'
what(): Failed to set TLS value: Invalid argument
Aborted (core dumped)
If I enter this command:
anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
[ 2018-04-03 09:20:59] [launch.cpp:134@operator()] Anbox session manager service isn't running, trying to start it.
[ 2018-04-03 09:21:04] [launch.cpp:134@operator()] Anbox session manager service isn't running, trying to start it.
[ 2018-04-03 09:21:09] [launch.cpp:134@operator()] Anbox session manager service isn't running, trying to start it.
[ 2018-04-03 09:21:14] [launch.cpp:206@operator()] Couldn't get a connection with the session manager
What were you expecting?:
Hint to get anbox working under newest arch linux.
Additional info:
THANK YOU !
The text was updated successfully, but these errors were encountered: