You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, well done for this. However I did not run interactively -it to start the container. And now that itś running there seems no way to setup a new vnc password?
But also IDK where which folders this is gets written, for a persistant configuration between restarts. For example i would like to bind mount a docker volume onto that folder. To remount it and keep the vnc password setting. So that the container can be re-created. But still keep that initial setup.
What i tried:
I can exec or sshinto the container as root. And see the running quemu process.
But when I do virsh list on the host (outside the container). Then nothing listed.
And doing virsh list inside the container --> gives an error message.
error: failed to connect to the hypervisor
error: Operation not supported: Cannot use direct socket mode if no URI is set
so maybe there is someting like a local unix socket in the container? to connect to, to gain access to that quemu session? or something like that?
This areas does not seem covered in docs just yet. So if you can give any small help would really appreciate that. Thank you!
The text was updated successfully, but these errors were encountered:
ok i have now tried docker attach to connect the tty to qemu-system. however when i type help nothing happens, there is no output. So maybe the io redirection has not worked.
so if you can shed any light on that it would be appreciated thanks
Hi there, well done for this. However I did not run interactively
-it
to start the container. And now that itś running there seems no way to setup a new vnc password?But also IDK where which folders this is gets written, for a persistant configuration between restarts. For example i would like to bind mount a docker volume onto that folder. To remount it and keep the vnc password setting. So that the container can be re-created. But still keep that initial setup.
What i tried:
exec
orssh
into the container asroot
. And see the running quemu process.virsh list
on the host (outside the container). Then nothing listed.virsh list
inside the container --> gives an error message.so maybe there is someting like a local unix socket in the container? to connect to, to gain access to that quemu session? or something like that?
This areas does not seem covered in docs just yet. So if you can give any small help would really appreciate that. Thank you!
The text was updated successfully, but these errors were encountered: