UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Network error when container starting - POCO F1

    Scheduled Pinned Locked Moved
    Waydroid
    3
    6
    690
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      presty80
      last edited by Keneda

      Hi,

      i have a problem with start container with Pocophone F1.
      Trying starting from app waydroid or by terminal commands the result is the same:

      waydroid status:
      Session: STOPPED
      Vendor type: HALIUM_9

      waydroid log:

      (009094) [17:49:26] Starting waydroid session
(009094) [17:49:26] XDG Session is not "wayland"
(009094) [17:49:26] % getprop ro.sf.lcd_density
440
(009094) [17:49:26] Save session config: /var/lib/waydroid/session.cfg
(009094) [17:49:26] UserMonitor service is not even started
(009094) [17:49:26] Clipboard service is not even started
(008855) [17:49:27] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start

dnsmasq: unknown interface waydroid0
Failed to setup waydroid-net.
Failed to setup waydroid-net.
(008855) [17:49:27] % umount /var/lib/waydroid/rootfs/vendor/waydroid.prop
(008855) [17:49:27] % umount /var/lib/waydroid/rootfs/vendor/lib64/egl
(008855) [17:49:27] % umount /var/lib/waydroid/rootfs/vendor/lib/egl
(008855) [17:49:27] % umount /var/lib/waydroid/rootfs/vendor
(008855) [17:49:27] % umount /var/lib/waydroid/rootfs
(008855) [17:49:27] % mount /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(008855) [17:49:27] % mount -o remount,ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(008855) [17:49:27] % mount /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(008855) [17:49:28] % mount -o remount,ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(008855) [17:49:28] % mount -o bind /vendor/lib/egl /var/lib/waydroid/rootfs/vendor/lib/egl
(008855) [17:49:28] % mount -o bind /vendor/lib64/egl /var/lib/waydroid/rootfs/vendor/lib64/egl
(008855) [17:49:28] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(008855) [17:49:28] % start cgroup-lite
start: Job is already running: cgroup-lite
(008855) [17:49:28] % umount -l /sys/fs/cgroup/schedtune
umount: /sys/fs/cgroup/schedtune: mountpoint not found
(008855) [17:49:28] % stop nfcd
stop: Unknown instance: 
(008855) [17:49:28] % chmod 777 -R /dev/ashmem
(008855) [17:49:28] % chmod 777 -R /dev/dri
(008855) [17:49:28] % chmod 777 -R /dev/graphics
(008855) [17:49:28] % chmod 777 -R /dev/ion
(008855) [17:49:28] % chmod 777 -R /dev/fb0
(008855) [17:49:28] % chmod 777 -R /dev/video
(008855) [17:49:28] % chmod 777 -R /dev/video2
(008855) [17:49:28] % chmod 777 -R /dev/video1
(008855) [17:49:28] % chmod 777 -R /dev/video0
(008855) [17:49:28] % chmod 777 -R /dev/video33
(008855) [17:49:28] % chmod 777 -R /dev/video32
(008855) [17:49:28] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(008855) [17:49:28] New background process: pid=9301, output=background
lxc-start: network.c: lxc_ovs_attach_bridge: 1817 Failed to attach "waydroid0" to openvswitch bridge "vethUGJ9UI": lxc-start:
lxc-start: network.c: instantiate_veth: 201 Failed to attach "vethUGJ9UI" to bridge "waydroid0": Operation not permitted
lxc-start: network.c: lxc_create_network_priv: 2378 Failed to create network device
lxc-start: start.c: lxc_spawn: 1522 Failed to create the network.
lxc-start: start.c: __lxc_start: 1802 Failed to spawn container "waydroid".
lxc-start: conf.c: run_buffer: 286 Script exited with status 126.
lxc-start: start.c: lxc_fini: 920 Failed to run lxc.hook.post-stop for container "waydroid".
The container failed to start.
Additional information can be obtained by setting the --logfile and --logpriority options.
(008855) [17:49:28] waiting 10 seconds for container to start...
(008855) [17:49:29] waiting 9 seconds for container to start...
(008855) [17:49:30] waiting 8 seconds for container to start...
(008855) [17:49:31] waiting 7 seconds for container to start...
(008855) [17:49:32] waiting 6 seconds for container to start...
(008855) [17:49:33] waiting 5 seconds for container to start...
(008855) [17:49:34] waiting 4 seconds for container to start...
(008855) [17:49:35] waiting 3 seconds for container to start...
(008855) [17:49:36] waiting 2 seconds for container to start...
(008855) [17:49:37] waiting 1 seconds for container to start...
(008855) [17:49:38] ERROR: container failed to start
(008855) [17:49:38] See also: <https://github.com/waydroid>
(008855) [17:49:38] Traceback (most recent call last):
  File "/usr/lib/waydroid/tools/__init__.py", line 69, in main
    actions.container_manager.start(args)
  File "/usr/lib/waydroid/tools/actions/container_manager.py", line 163, in start
    raise OSError("container failed to start")
OSError: container failed to start

(009409) [17:49:39] UserMonitor service is not even started
(009409) [17:49:39] Clipboard service is not even started
(009410) [17:49:39] % chmod 666 -R /dev/anbox-binder
(009410) [17:49:39] % chmod 666 -R /dev/anbox-vndbinder
(009410) [17:49:39] % chmod 666 -R /dev/anbox-hwbinder
(009410) [17:49:39] Container manager is waiting for session to load
(009094) [17:49:39] UserMonitor service is not even started
(009094) [17:49:39] Clipboard service is not even started

      Someone could help me ?
      Thank you

      KenedaK J 2 Replies Last reply Reply Quote 0
      • KenedaK
        Keneda @presty80
        last edited by

        @presty80
        I edited your post so it is more readable.
        Please use code tag next time ā˜ŗ
        Use the </> button to do so.

        2015-2023 : Meizu MX4 now in legacy drawer by lack of pristine battery šŸ˜«
        2023-***** : Nexus 5 (16.04 OTA 25) for daily use, slowly dying šŸ¤•
        2024-***** : Fairphone 5 waiting UT for freedom šŸ˜‰
        šŸ‡²šŸ‡«šŸ‡¬šŸ‡§

        P 1 Reply Last reply Reply Quote 1
        • P
          presty80 @Keneda
          last edited by presty80

          Solved!

          Installation was not yet completed.
          Uninstalling and reinstalling waydroid solved my problem.

          1 Reply Last reply Reply Quote 0
          • J
            jhayar0719 @presty80
            last edited by

            @presty80 same issue here using redmi note 8 pro with hallium 10

            KenedaK 1 Reply Last reply Reply Quote 0
            • KenedaK
              Keneda @jhayar0719
              last edited by

              @jhayar0719
              Maybe same solution ?

              2015-2023 : Meizu MX4 now in legacy drawer by lack of pristine battery šŸ˜«
              2023-***** : Nexus 5 (16.04 OTA 25) for daily use, slowly dying šŸ¤•
              2024-***** : Fairphone 5 waiting UT for freedom šŸ˜‰
              šŸ‡²šŸ‡«šŸ‡¬šŸ‡§

              J 1 Reply Last reply Reply Quote 0
              • J
                jhayar0719 @Keneda
                last edited by

                @keneda said in Network error when container starting - POCO F1:

                solution

                im afraid not , but its okay i found the solution , updating UT to latest stable branch fix the issue on redmi note 8 pro

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post