Running weston 10 without weston-launch on containers

This is not an issue, I think. If I'm posting in the wrong place, please let me know the right way to make this question. Before Weston 10 I used weston-launch inside containers without problems. Now on Weston 10 I saw that weston-launch is deprecated, and not included as default. I tried to use the seatd-launch without success:

 seatd-launch -- weston --backend=drm-backend.so --tty=/dev/tty7 --user=torizon
00:00:00.000  [seatd/seat.c:39] Created VT-bound seat seat0
00:00:00.007  [seatd/seatd.c:194] seatd started
Date: 2022-09-23 UTC
[04:35:14.132] weston 10.0.1
               https://wayland.freedesktop.org
               Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
               Build: 10.0.1
[04:35:14.136] Command line: weston --backend=drm-backend.so --tty=/dev/tty7 --user=torizon
[04:35:14.136] OS: Linux, 5.19.0-nezha, #1 PREEMPT Wed Sep 14 05:26:45 UTC 2022, riscv64
[04:35:14.137] Flight recorder: enabled
[04:35:14.137] warning: XDG_RUNTIME_DIR "/tmp/1000-runtime-dir" is not configured
correctly.  Unix access mode must be 0700 (current mode is 0700),
and must be owned by the user UID 0 (current owner is UID 1000).
Refer to your distribution on how to get it, or
http://www.freedesktop.org/wiki/Specifications/basedir-spec
on how to implement it.
[04:35:14.140] Using config file '/etc/xdg/weston/weston.ini'
[04:35:14.144] Output repaint window is 7 ms maximum.
[04:35:14.146] Loading module '/usr/lib/riscv64-linux-gnu/libweston-10/drm-backend.so'
[04:35:14.186] initializing drm backend
[04:35:14.188] Trying logind launcher...
[04:35:14.192] logind: cannot find systemd session for uid: 0 -61
[04:35:14.194] logind: cannot setup systemd-logind helper error: (No data available), using legacy fallback
[04:35:14.197] Trying weston_launch launcher...
[04:35:14.197] could not get launcher fd from env
[04:35:14.199] Trying direct launcher...
[04:35:14.201] <stdin> not a vt
[04:35:14.201] if running weston from ssh, use --tty to specify a tty
[04:35:14.201] fatal: drm backend should be run using weston-launch binary, or your system should provide the logind D-Bus API.
[04:35:14.202] fatal: failed to create compositor backend
Internal warning: debug scope 'drm-backend' has not been destroyed.
00:00:00.198  [seatd/seatd.c:218] seatd stopped

I'm pretty sure I'm missing something here, but weston tells me i should have weston-launch ...