Poky login when preparing new virtual device on Windows

General Discussions
1

Hi! I am trying to set up a new virtual device as the documentation says. But when running the command, it pulls the mender image, runs the image, but it appears this: Starting Mender-configure device configuration…
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Started Serial Getty on ttyS1.
[ OK ] Reached target Login Prompts.
[ OK ] Started System Logging Service.
Starting User Login Management…
Starting OpenSSH Key Generation…
[ OK ] Started D-Bus System Message Bus.
[ OK ] Finished IPv6 Packet Filtering Framework.

Poky (Yocto Project Reference Distro) 4.0.5 qemux86-64 ttyS0

qemux86-64 login: [ OK ] Finished IPv4 Packet Filtering Framework.

And then, no pending device to be accepted shows on the workstation.
Any solution?

2

Hi @Rubitor5,

Thanks for reaching out! I just tried to replicate this and found that the setup is a bit complicated for Windows. The form I used is

  • Docker utilizing WSL2
  • Git Bash as terminal, as PowerShell doesn’t accept the copy-pasted instructions.

Then I started the container up by just pasting the snippet from my account as explained in the documentation, and after about 3-5 Minutes the virtual device was ready to accept in the dashboard.

If this does not happen for you in some time, can you try to log into the virtual device - user root, no password - and then check the logs with journalctl -u mender-client? This might give us some hints.

Greetz,
Josef

3

I’ve run the command at git bash and logged in with root and this shows:
[ OK ] Started System Logging Service.
Starting User Login Management…
Starting OpenSSH Key Generation…
[ OK ] Started D-Bus System Message Bus.
[ OK ] Finished IPv6 Packet Filtering Framework.
[ OK ] Finished IPv4 Packet Filtering Framework.

Poky (Yocto Project Reference Distro) 4.0.5 qemux86-64 ttyS0

qemux86-64 login: root
root@qemux86-64:~# journalctl -u mender-client
– No entries –
root@qemux86-64:~#

4

That’s definitely strange @Rubitor5. Can you check if the container has connectivity, like pinging google.com? And the Mender client is there?

If you can send me the getting started snippet (via direct message) that you used then I can spin up one too.

Greetz
Josef

5

I think there’s no connectivity:
root@qemux86-64:~# ping google.com
PING google.com(::ffff:142.250.185.14 (::ffff:142.250.185.14)) 56 data bytes

^C— google.com ping statistics —
28 packets transmitted, 0 received, 100% packet loss, time 27635ms

6

This is the get started snippet I followed: Prepare a virtual device | Mender documentation

7

Nonetheless, when I ping mender it receives response:
root@qemux86-64:~# ping eu.hosted.mender.io
PING eu.hosted.mender.io (108.142.217.178) 56(84) bytes of data.
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=1 ttl=255 time=294 ms
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=2 ttl=255 time=227 ms
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=3 ttl=255 time=99.4 ms
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=4 ttl=255 time=173 ms
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=5 ttl=255 time=147 ms
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=6 ttl=255 time=203 ms
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=7 ttl=255 time=72.1 ms
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=8 ttl=255 time=111 ms
64 bytes from 108.142.217.178 (108.142.217.178): icmp_seq=9 ttl=255 time=102 ms