Mirto Busico's questions

当我尝试snap install microk8s在 LXD 机器上运行时，它无法启动并产生以下错误：

sysop@hoseplavm:~$ lxc list
+------------+---------+----------------------+------+------------+-----------+
|    NAME    |  STATE  |         IPV4         | IPV6 |    TYPE    | SNAPSHOTS |
+------------+---------+----------------------+------+------------+-----------+
| kubernetes | RUNNING | 10.144.28.123 (eth0) |      | PERSISTENT |           |
+------------+---------+----------------------+------+------------+-----------+
sysop@hoseplavm:~$ lxc exec kubernetes bash
root@kubernetes:~# microk8s.inspect
Inspecting services
Service snap.microk8s.daemon-containerd is running
Service snap.microk8s.daemon-apiserver is running
FAIL:  Service snap.microk8s.daemon-proxy is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-proxy
FAIL:  Service snap.microk8s.daemon-kubelet is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-kubelet
Service snap.microk8s.daemon-scheduler is running
Service snap.microk8s.daemon-controller-manager is running
Service snap.microk8s.daemon-etcd is running
Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system info
Copy network configuration to the final report tarball
Copy processes list to the final report tarball
Copy snap list to the final report tarball
Inspect kubernetes cluster

Building the report tarball
Report tarball is at /var/snap/microk8s/522/inspection-report-20190604_133500.tar.gz
root@kubernetes:~#

是否可以在 LXD 容器内安装 microk8s？

我需要知道部署 charmed-kubernetes 魅力的硬件要求是什么。

我在此配置上尝试失败（安装永远不会结束）：

硬件：配备 Intel i7 和 32Gb RAM 的笔记本电脑

虚拟机：三个 kvm 虚拟机，带有 8 个处理器和 8Gb RAM

云：三节点 LXD 集群

运行 juju 的控制工作站

所有机器都有 Kubuntu 18.04。LXD 是 3.12 版 snap 安装

我使用了命令

juju deploy charmed-kubernetes

3小时后，该过程从未结束。

从硬件完全重新启动后，我最终遇到了这种情况：

Model    Controller          Cloud/Region        Version  SLA          Timestamp
default  lxd-remote-default  lxd-remote/default  2.6.2    unsupported  10:50:30+02:00

App                    Version  Status   Scale  Charm                  Store       Rev  OS      Notes
easyrsa                3.0.1    active     0/1  easyrsa                jujucharms  248  ubuntu  
etcd                   3.2.10   active       3  etcd                   jujucharms  426  ubuntu  
flannel                0.10.0   active     1/3  flannel                jujucharms  417  ubuntu  
kubeapi-load-balancer  1.14.0   active     0/1  kubeapi-load-balancer  jujucharms  642  ubuntu  exposed
kubernetes-master      1.14.2   waiting    1/2  kubernetes-master      jujucharms  678  ubuntu  
kubernetes-worker      1.14.2   waiting    2/3  kubernetes-worker      jujucharms  536  ubuntu  exposed

Unit                     Workload     Agent      Machine  Public address  Ports     Message
easyrsa/0                unknown      lost       0        240.12.0.59               agent lost, see 'juju show-status-log easyrsa/0'
etcd/0                   active       idle       1        240.13.0.77     2379/tcp  Healthy with 3 known peers
etcd/1*                  active       idle       2        240.11.0.3      2379/tcp  Errored with 0 known peers
etcd/2                   active       idle       3        240.11.0.51     2379/tcp  Errored with 0 known peers
kubeapi-load-balancer/0  unknown      lost       4        240.12.0.125    443/tcp   agent lost, see 'juju show-status-log kubeapi-load-balancer/0'
kubernetes-master/0*     waiting      executing  5        240.13.0.62     6443/tcp  (leader-elected) Waiting for 6 kube-system pods to start
flannel/1*             active       idle                240.13.0.62               Flannel subnet 10.1.90.1/24
kubernetes-master/1      unknown      lost       6        240.12.0.115    6443/tcp  agent lost, see 'juju show-status-log kubernetes-master/1'
flannel/0              unknown      lost                240.12.0.115              agent lost, see 'juju show-status-log flannel/0'
kubernetes-worker/0*     maintenance  executing  7        240.13.0.144              (upgrade-charm) Checking resources
kubernetes-worker/1      maintenance  executing  8        240.13.0.82               (upgrade-charm) Checking resources
kubernetes-worker/2      unknown      lost       9        240.12.0.106              agent lost, see 'juju show-status-log kubernetes-worker/2'
flannel/2              unknown      lost                240.12.0.106              agent lost, see 'juju show-status-log flannel/2'

Machine  State    DNS           Inst id        Series  AZ  Message
0        down     240.12.0.59   juju-1627e9-0  bionic      Stopped
1        started  240.13.0.77   juju-1627e9-1  bionic      Running
2        started  240.11.0.3    juju-1627e9-2  bionic      Running
3        started  240.11.0.51   juju-1627e9-3  bionic      Running
4        down     240.12.0.125  juju-1627e9-4  bionic      Stopped
5        started  240.13.0.62   juju-1627e9-5  bionic      Running
6        down     240.12.0.115  juju-1627e9-6  bionic      Stopped
7        started  240.13.0.144  juju-1627e9-7  bionic      Running
8        started  240.13.0.82   juju-1627e9-8  bionic      Running
9        down     240.12.0.106  juju-1627e9-9  bionic      Stopped

sysop@kvmnode0:~$ 

而且我看到了对硬盘的计数访问。

根据我过去的经验，这表明硬件不足以完成安装。

那么，部署 charmed Kubernetes 的最低硬件要求是什么？

我正在遵循The charmed distribution of kubernetes 中的说明

但似乎 kubernetes 咒语不存在

sysop@kvmnode1:~$ sudo snap install conjure-up --classic
[sudo] password di sysop: 
conjure-up 2.6.7-20190521.1305 from Canonical✓ installed
sysop@kvmnode1:~$ conjure-up canonical-kubernetes
[error] Can't find a spell matching 'canonical-kubernetes'

如何使用 conjure-up 安装 Kubernetes？

我发现了 2 个与“kubernetes 的迷人分布”相关的魅力。

https://jujucharms.com/canonical-kubernetes/上的第一个似乎只有必要的组件。

https://jujucharms.com/canonical-kubernetes/2的第二个添加了 topbeat filebeat 弹性搜索和 kibana。

奇怪的是，这两个魅力说它们是用命令“juju deploy canonical-kubernetes”安装的

所以我的问题：

• 什么是正确的魅力？
• 使用命令“juju deploy canonical-kubernetes”会安装什么魅力？

谢谢

我有一台带有 LXD来宾（基于 ubuntu18.04 映像）的主机（KVM 和 Kubuntu 18.04 ）。

我可以从客人SSH到主机。

但是尝试从主机到访客的 ssh 会给出一个

权限被拒绝（公钥）

错误

重现步骤：

• lxc exec 进入来宾
• 使用 ubuntu 用户执行登录（避免 root 权限问题）
• ssh 到主机 -成功
• 退出表单用户 ubuntu - 退出来宾
• 从主机 ssh 到 ubuntu@guest -错误

我做错了什么？

在完整的会话记录下方

sysop@kvmneo4j:~$ lxc list
+----------+---------+-------------------+------+------------+-----------+
|   NAME   |  STATE  |       IPV4        | IPV6 |    TYPE    | SNAPSHOTS |
+----------+---------+-------------------+------+------------+-----------+
| base1804 | RUNNING | 10.0.0.205 (eth0) |      | PERSISTENT | 0         |
+----------+---------+-------------------+------+------------+-----------+
sysop@kvmneo4j:~$ lxc exec base1804 bash
root@base1804:~# exec login ubuntu
Password: 
Last login: Wed Jan  2 18:58:10 UTC 2019 on UNKNOWN
Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-43-generic x86_64)

* Documentation:  https://help.ubuntu.com
* Management:     https://landscape.canonical.com
* Support:        https://ubuntu.com/advantage

System information as of Wed Jan  2 19:02:28 UTC 2019

System load:    1.69      Processes:           22
Usage of /home: unknown   Users logged in:     0
Memory usage:   1%        IP address for eth0: 10.0.0.205
Swap usage:     0%


Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.

Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings


To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@base1804:~$ ssh [email protected]
[email protected]'s password: 
Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-43-generic x86_64)

* Documentation:  https://help.ubuntu.com
* Management:     https://landscape.canonical.com
* Support:        https://ubuntu.com/advantage


* Canonical Livepatch is available for installation.
- Reduce system reboots and improve kernel security. Activate at:
    https://ubuntu.com/livepatch
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings

Last login: Wed Jan  2 19:58:42 2019 from 10.0.0.205
sysop@kvmneo4j:~$ logout
Connection to 10.0.0.1 closed.
ubuntu@base1804:~$ logout
sysop@kvmneo4j:~$ ssh -v [email protected]
OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n  7 Dec 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 10.0.0.205 [10.0.0.205] port 22.
debug1: Connection established.
debug1: identity file /home/sysop/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/sysop/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/sysop/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/sysop/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/sysop/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/sysop/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/sysop/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/sysop/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.1
debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 10.0.0.205:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:i0Ezo01qJyhIue4PIRobOw/qKuvDW/7OJZzgB0X5jGM
debug1: Host '10.0.0.205' is known and matches the ECDSA host key.
debug1: Found key in /home/sysop/.ssh/known_hosts:1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: RSA SHA256:EfYKpv5N+M8YBgCFjjy3P9M0jYt7DObq9ApoZ0G8qL4 /home/sysop/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/sysop/.ssh/id_dsa
debug1: Trying private key: /home/sysop/.ssh/id_ecdsa
debug1: Trying private key: /home/sysop/.ssh/id_ed25519
debug1: No more authentication methods to try.
[email protected]: Permission denied (publickey).
sysop@kvmneo4j:~$ 

我创建了一个 Ubuntu 容器

lxc launch ubuntu images:ubuntu/xenial mycontainer

我可以使用访问容器

lxc exec mycontainer bash

我发现 mysel 以 root 身份登录而没有询问任何密码

我看到有一个“ubuntu”用户定义

如何访问安装在容器（例如 webmin）中的要求用户名和密码的软件？

什么是默认密码？