Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installed in Ubuntu Ubuntu 20.04.2.0 LTS server version failed #27

Open
maoyang opened this issue Jul 10, 2021 · 8 comments
Open

Installed in Ubuntu Ubuntu 20.04.2.0 LTS server version failed #27

maoyang opened this issue Jul 10, 2021 · 8 comments

Comments

@maoyang
Copy link

maoyang commented Jul 10, 2021

my installation log

[qlauncher][INFO] 2021-07-10T13:57:09Z Start install k3s
[OK] Install k3s
[qlauncher][INFO] 2021-07-10T13:57:25Z Create service file
[qlauncher][INFO] 2021-07-10T13:57:25Z systemd: Creating service file /etc/systemd/system/qlauncher.service
[qlauncher][INFO] 2021-07-10T13:57:25Z systemd: Creating service env file /usr/local/bin/qlauncher.env
[qlauncher][INFO] 2021-07-10T13:57:25Z systemd: Enabling qlauncher unit
[qlauncher][INFO] 2021-07-10T13:57:26Z systemd: Starting qlauncher
Job for qlauncher.service failed because the control process exited with error code.
See "systemctl status qlauncher.service" and "journalctl -xe" for details.

@maoyang
Copy link
Author

maoyang commented Jul 10, 2021

I executed systemctl status qlauncher.service the got the result

qlauncher.service - qlauncher version 2
Loaded: loaded (/etc/systemd/system/qlauncher.service; enabled; vendor preset: enabled)
Active: activating (start) since Sat 2021-07-10 14:01:18 UTC; 478ms ago
Process: 20598 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
Process: 20608 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Cntrl PID: 20610 (qlauncher.sh)
Tasks: 2
Memory: 4.2M
CGroup: /system.slice/qlauncher.service
├─20610 /bin/bash /opt/qlauncherV2/qlauncher.sh restart
└─20686 /bin/sleep 10

Jul 10 14:01:18 swar systemd[1]: Starting qlauncher version 2...
Jul 10 14:01:18 swar qlauncher.sh[20618]: [qlauncher][INFO] 2021-07-10T14:01:18Z Detect sudo/root user
Jul 10 14:01:18 swar qlauncher.sh[20618]: [qlauncher][INFO] 2021-07-10T14:01:18Z [OK] User has sudo/root access right
Jul 10 14:01:18 swar qlauncher.sh[20618]: [qlauncher][INFO] 2021-07-10T14:01:18Z Stop qlauncherV2

@coderkk
Copy link
Collaborator

coderkk commented Jul 12, 2021

I think maybe the issue with your network setting. Please re-check again your network. Thank you.

@maoyang
Copy link
Author

maoyang commented Jul 12, 2021

Thanks for your online supporting ,I've resolved network DNS setting issue ,and re-installed qlauncher follow by github readme ,but I got error message when did this step

/opt/qlauncherV2/qlauncher.sh status

then output

FATA[0010] failed to connect: failed to connect: context deadline exceeded

@coderkk
Copy link
Collaborator

coderkk commented Jul 12, 2021

Could you try uninstall qlauncher
sudo /opt/qlauncherV2/qlauncher.sh uninstall

Then run the install again
sudo /opt/qlauncherV2/qlauncher.sh install

@maoyang
Copy link
Author

maoyang commented Jul 12, 2021

I've followed your steps but the result is same

@coderkk
Copy link
Collaborator

coderkk commented Jul 12, 2021

Please check this file /etc/crictl.yaml exist or not?

If not exist, please try to create one.

# cat /etc/crictl.yaml
runtime-endpoint: unix:///run/containerd/containerd.sock
image-endpoint: unix:///run/containerd/containerd.sock
timeout: 2
debug: true
pull-image-on-create: false

Refer to this cri-o/cri-o#1922

@maoyang
Copy link
Author

maoyang commented Jul 12, 2021

yes the /etc/crictl.yaml didn't exist then I followed your steps and re-start qlauncher

I execute the command -->sudo /opt/qlauncherV2/qlauncher.sh status

output

DEBU[0000] ListContainerRequest: &ListContainersRequest{Filter:&ContainerFilter{Id:,State:nil,PodSandboxId:,LabelSelector:map[string]string{},},}
DEBU[0000] ListContainerResponse: nil
FATA[0000] listing containers failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService

@coderkk
Copy link
Collaborator

coderkk commented Jul 12, 2021

This issue occur because of the compatible between k3s's containerd and dockerd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants