https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
c
@jolly-forest-99711 any thoughts on what could be happening here?
j
Hmm, I have an rpm install on openSUSE Leap 15.3 that is working as far as I can tell. Let me try in a VM
I gave it another try in a rocky 8.7 with RD 1.7.0 installed via AppImage, and it appears to work fine
Have you taken a look in the logs directory (reachable via main RD application window via Troubleshooting > Show Logs)? Also, have you tried a restart? Doing a factory reset of RD?
If none of those things helps, it is probably best to open an issue... let me know how it goes
e
Thanks Adam. I have tried a factory reset of RD before and that didn't fix the issue. I just looked at the troubleshooting logs while I click on the button and I don't see any log messages being written to any logs. I guess I will try using the rpm on a openSUSE instead. Thanks
I found some error messages on the Rocky Linux /var/log/messages. The following messages appear every time I click on the "Read from File" button. I'm curious if this might be related to my desktop VM (Fedora desktop 37) from which I ssh into the physical server (Rocky Linux) and launch Rancher Image. The physical server doesn't have a graphical console. Just out of curiosity, I switch the desktop VM to a Ubuntu desktop 22.10. However I'm getting the exact same behavior in Rancher Desktop and the same messages on the physical host. 
Jan 16 16:49:15 glx9 systemd[2659]: Starting Portal service (GTK/GNOME implementation)...
Jan 16 16:49:15 glx9 journal[2374034]: cannot open display:
Jan 16 16:49:15 glx9 systemd[2659]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Jan 16 16:49:15 glx9 systemd[2659]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Jan 16 16:49:15 glx9 systemd[2659]: Failed to start Portal service (GTK/GNOME implementation).
Jan 16 16:49:15 glx9 systemd[2659]: Starting Portal service (GTK/GNOME implementation)...
Jan 16 16:49:15 glx9 journal[2374035]: cannot open display:
Jan 16 16:49:15 glx9 systemd[2659]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Jan 16 16:49:15 glx9 systemd[2659]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Jan 16 16:49:15 glx9 systemd[2659]: Failed to start Portal service (GTK/GNOME implementation).
Jan 16 16:49:15 glx9 journal[2834]: Backend call failed: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
j
So you are trying to run Rancher Desktop on a machine that doesn't have any desktop installed? I suspect that is the problem. AFAIK we only support desktop environments at the moment - @fast-garage-66093 do you know if we have any plans to support command line only environments? The good news is that there are a lot of alternatives, depending on what you're trying to do: 
nerdctl
, 
docker
, 
minikube
, 
k3s
, and 
podman
come to mind
Also, in case you aren't aware, Rancher Desktop is intended to be used in development. If you're trying to run something in production, you probably want to use a different tool
f
@jolly-forest-99711 We don't have any plans right now to support systems that cannot run the GUI at all. We do want to be able to control the RD engine via 
rdctl
, so everything can be automated, but the app itself need to be able to run the GUI code, even if the user doesn't intend to interact with it directly.
e
I think I confused you. I have a working desktop environment, gnome or kde. It should work with a remote Rancher Desktop through X-window, right? As I said, the GUI works for the most part. The only issue I encountered is the "Read from File" button.
f
@jolly-forest-99711 is this some possible problem with the AppImage version of not being able to read from the local filesystem maybe?
The reading would likely happen in the 
steve
process and not the 
electron
one
j
is this some possible problem with the AppImage version
Maybe, but I could not reproduce the problem on my Rocky 8.7 VM. It could be a Rocky 9 thing, but I feel like the problem is related to what @elegant-action-27521 is doing
f
@elegant-action-27521 Did you try different file system locations? Can you give example location for @jolly-forest-99711 to verify? There is not much we can do unless we can repro the issue
j
@elegant-action-27521 I don't know if Rancher Desktop should work remotely through X-window, I've never tried it... it certainly wasn't a use case we envisioned. If this is something that is important to you, I think it would be best to create an issue for this. I suspect it will take a while to understand what is going on here
e
It's not an important issue but just trying to understand if it's my env or Rancher Desktop itself. I can try to install Rancher Desktop on an RHEL 8.7 system. That should be very close to Rocky 8.7. Will try using a different location as well if RHEL doesn't work. Will keep you posted. Thanks
The "Read from File" button works on RHEL 8.7. So this is related to Rocky 9,x (possibly RHEL 9.x as well).
j
Very interesting. Sounds like a bug then. Would you mind creating an issue?
e
Yes I will create an issue.
j
Thanks!
54 Views
Open in Slack
PreviousNext
Powered by