Do you know how to connect the desktop of this Docker container as a Singularity container through Remote Desktop?
Linux - ContainersThis forum is for the discussion of all topics relating to Linux containers. Docker, LXC, LXD, runC, containerd, CoreOS, Kubernetes, Mesos, rkt, and all other Linux container platforms are welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We can download this Docker container as a Singularity container using this command: `singularity pull docker://quay.io/cosmoscloud/ubuntu-gnome:rdp`.
If I shell into the container without sudo, I don't know how to start the xrdp service because I don't have sudo permission. So, I shell into the container with sudo and change the port to 3390 in file `/etc/xrdp/xrdp.ini` because 3389 is already occupied. Then I run `sudo systemctl restart xrdp`, and I receive the following output:
Quote:
Running in chroot, ignoring request: restart
If I run `systemctl enable xrdp`, I'll receive the following output:
Quote:
Synchronizing state of xrdp.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable xrdp
I don't know whether these messages indicate that the Remote Desktop service is started successfully, but I cannot connect it. Can you help me by showing how to connect through the Remote Desktop? PS, this container also installed TigerVNC, but I can't connect either.
I don't really understand how do you "shell into the container*with sudo". What does it mean?
If you are already root you do not need to use sudo before systemctl (or any other command).
I don't really understand how do you "shell into the container*with sudo". What does it mean?
If you are already root you do not need to use sudo before systemctl (or any other command).
Let's not worry about the technical details of sudo thing. Let's assume your boss asked you to connect the GUI desktop of this container using singularity through RDP or VNC. What will you do?
This sounds like an “XY problem.” Please tell us exactly what your boss wants you to do, not how you propose to do it.
“Containers,” actually, are “an illusion.” You are actually operating as a non-privileged (I hope!) process. Therefore, you cannot execute commands which affect “the environment,” even though you might believe the illusion and therefore expect to do so.
By “illusion,” I’m being very specific: the “containerized” process doesn’t realize that he is, in fact, “an ordinary, non-privileged process,” running on some host somewhere, whose actual topology he has no concept of. (And, if “the illusion” is complete – as it is – he doesn’t care.)
The illusion necessarily falters when you attempt to do something, “within the container [illusion …],” which might actually affect the environment.
Last edited by sundialsvcs; 01-19-2024 at 12:13 PM.
This sounds like an “XY problem.” Please tell us exactly what your boss wants you to do, not how you propose to do it.
“Containers,” actually, are “an illusion.” You are actually operating as a non-privileged (I hope!) process. Therefore, you cannot execute commands which affect “the environment,” even though you might believe the illusion and therefore expect to do so.
By “illusion,” I’m being very specific: the “containerized” process doesn’t realize that he is, in fact, “an ordinary, non-privileged process,” running on some host somewhere, whose actual topology he has no concept of. (And, if “the illusion” is complete – as it is – he doesn’t care.)
The illusion necessarily falters when you attempt to do something, “within the container [illusion …],” which might actually affect the environment.
I have no idea what you mean by “XY problem.” But maybe you should've labelled a previous reply as "XY answer".
I believe I have said everything very clearly in my question. If anyone has difficulty understanding English, please simply leave my question instead of making deviated reply.
From your answer, it is obvious that you do not know what a container and in particular what a Singularity container is and how to work with it. I have no interest in wasting time explaining those basic concepts to you. Please leave my question to others who are technically competent to answer my question. Thanks.
this is the direct translation of that last part (by google):
Quote:
Let me add a few words, I'm here to ask questions, not to argue with you idiots. Quarreling really doesn't mean anything to me. If you don't want to help me answer the question, it doesn't matter. You can just go. I won't beg for your help. You guys are not very capable and have a bad temper. To be honest, I don’t expect you to be able to help me with anything at all, especially when you reach the Guru level, just like the Nine-Pocket Elder of the Beggar Clan, how can most of your abilities be improved? People, real martial arts are rare and ordinary. So much for that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.