I have to add my own CA certificate inside a docker container.

When I try to run the command "dpkg-reconfigure ca-certificates" inside the Dockerfile it fails because cannot use the interactive interface.

How can I run interactively inside the dockerfile?

Or is it possible to tell "dpkg-reconfigure ca-certificates" to enable all certificates without asking?

This is the Dockerfile:

# Docker Image which is used as foundation to create
# a custom Docker Image with this Dockerfile
FROM node:15

ENV NODE_EXTRA_CA_CERTS=/usr/src/app/mrootca.pem
ENV TERM=xterm

# A directory within the virtualized Docker environment
# Becomes more relevant when using Docker Compose later
WORKDIR /usr/src/app

# install CA cetificare in the OS
COPY ./mrootca.pem /usr/share/ca-certificates/mrootca.crt
RUN dpkg-reconfigure ca-certificates
 
# Copies package.json and package-lock.json to Docker environment
COPY package*.json ./
COPY mrootca.pem ./
 
# Installs all node packages
RUN npm install
 
# Copies everything over to Docker environment
COPY . .
 
# Uses port which is used by the actual application
EXPOSE 3000
 
# Finally runs the application
CMD [ "npm", "start" ]

The docker image is generated with the command:

docker build --tag fpresenter:v1 .

I need to know what are the hardware requirements to deploy the charmed-kubernetes charm.

I tried unsuccessfully (installation never ends) on this configuration:

hardware: notebook with Intel i7 and 32Gb RAM

VM: three kvm vm with 8 processors and 8Gb RAM

Cloud: three node LXD cluster

Controlling workstation on which juju is run

All machines have Kubuntu 18.04. LXD is version 3.12 snap installed

I used the command

juju deploy charmed-kubernetes

After 3 hours the process never ended.

After a complete restart from the hardware I end up in this situation:

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:~$ 

And I see a countinous access to the hard disk.

In my past experience this indicates insufficient hardware to complete the installation.

So, what are the minimum hardware requirements to deploy charmed kubernetes?

I'm following the instructions at The charmed distribution of kubernetes

But seems that the kubernetes spell doesn't exist

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'

How can I install kubernetes using conjure-up?

I'm trying to bootstrap juju on a lxd cluster cloud

Here the transcript of the command

sysop@kvmnode1:~/SVILUPPO/for_juju$ sudo juju bootstrap lxd-cloud                                                                                                              
Creating Juju controller "lxd-cloud-default" on lxd-cloud/default                                                                                                              
Looking for packaged Juju agent version 2.6.2 for amd64                                                                                                                        
To configure your system to better support LXD containers, please see: https://github.com/lxc/lxd/blob/master/doc/production-setup.md                                          
Launching controller instance(s) on lxd-cloud/default...
 - Create container from image: Failed to set apply_template volatile key: Failed to update database: failed to begin transaction: failed to create dqlite connection: no avail - juju-b3db51-0 (arch=amd64)          
Installing Juju agent on bootstrap instance
Fetching Juju GUI 2.14.0
Waiting for address
Attempting to connect to 240.11.0.27:22
Connected to 240.11.0.27
Running machine configuration script...
Bootstrap agent now started
Contacting Juju controller at 240.11.0.27 to verify accessibility...

Bootstrap complete, controller "lxd-cloud-default" now is available
Controller machines are in the "controller" model
Initial model "default" added
sysop@kvmnode1:~/SVILUPPO/for_juju$

Juju is installed by snap and is version 2.6.2

LXD is version 3.13

The lxd cluster is on 3 kvm virtual machines. All os host and guests are Kubuntu 18.04 updated today.

What this error means?

How can avoid it?

I have a LXC cluster with three nodes that are all KVM virtual machines with Kubuntu 18.04 with LXD 3.0.3 installed via apt

Also the host machine is a Kubuntu 18.04

I installed LXD on the first node (kvmnode1) and then I joined to the cluster the other two nodes (kvmnode2, kvmnode3)

Then I verified that starting the nodes from the first to the last (waiting for every node to complete the startup) and closing the nodes from the last to the first always gives a fully oerational cluster

Today I forgot to wait for the complete startup of every node and I ended up with a cluster with the first node non starting LXD end the other 2 nodes working correctly

On the failing first node I see

sysop@kvmnode1:~/Scaricati$ sudo systemctl status lxd
[sudo] password di sysop: 
● lxd.service - LXD - main daemon
   Loaded: loaded (/lib/systemd/system/lxd.service; indirect; vendor preset: enabled)
   Active: activating (start-post) (Result: exit-code) since Mon 2019-04-22 10:36:10 CEST; 1min 47s ago
     Docs: man:lxd(1)
  Process: 1592 ExecStart=/usr/bin/lxd --group lxd --logfile=/var/log/lxd/lxd.log (code=exited, status=1/FAILURE)
  Process: 1560 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load (code=exited, status=0/SUCCESS)
 Main PID: 1592 (code=exited, status=1/FAILURE); Control PID: 1593 (lxd)
    Tasks: 8
   CGroup: /system.slice/lxd.service
           └─1593 /usr/lib/lxd/lxd waitready --timeout=600

apr 22 10:36:10 kvmnode1 systemd[1]: Starting LXD - main daemon...
apr 22 10:36:10 kvmnode1 lxd[1592]: t=2019-04-22T10:36:10+0200 lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored."
apr 22 10:36:19 kvmnode1 lxd[1592]: t=2019-04-22T10:36:19+0200 lvl=eror msg="Failed to start the daemon: failed to open cluster database: failed to ensure schema: failed to update node version info: upda
apr 22 10:36:19 kvmnode1 lxd[1592]: Error: failed to open cluster database: failed to ensure schema: failed to update node version info: updated 0 rows instead of 1
apr 22 10:36:19 kvmnode1 systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
sysop@kvmnode1:~/Scaricati$ 

And on the second node I see

sysop@kvmnode2:~$ lxc cluster list
+----------+-----------------------------+----------+---------+----------------------------------------+
|   NAME   |             URL             | DATABASE |  STATE  |                MESSAGE                 |
+----------+-----------------------------+----------+---------+----------------------------------------+
| kvmnode1 | https://192.168.201.11:8443 | YES      | OFFLINE | no heartbeat since 134h36m2.926365228s |
+----------+-----------------------------+----------+---------+----------------------------------------+
| kvmnode2 | https://192.168.201.12:8443 | YES      | ONLINE  | fully operational                      |
+----------+-----------------------------+----------+---------+----------------------------------------+
| kvmnode3 | https://192.168.201.13:8443 | YES      | ONLINE  | fully operational                      |
+----------+-----------------------------+----------+---------+----------------------------------------+
sysop@kvmnode2:~$

What can I do to have kvmnode1 starting correctly and join the cluster?

P.S. I tried to start/stop the three nodes in every sequence but I always end in the same status

UPPDATE

I tried to start lxd in debug mode and it report the same failure

sysop@kvmnode1:~$ sudo lxd --debug --group lxd
DBUG[04-22|12:19:42] Connecting to a local LXD over a Unix socket 
DBUG[04-22|12:19:42] Sending request to LXD                   method=GET url=http://unix.socket/1.0 etag=
INFO[04-22|12:19:42] LXD 3.0.3 is starting in normal mode     path=/var/lib/lxd
INFO[04-22|12:19:42] Kernel uid/gid map: 
INFO[04-22|12:19:42]  - u 0 0 4294967295 
INFO[04-22|12:19:42]  - g 0 0 4294967295 
INFO[04-22|12:19:42] Configured LXD uid/gid map: 
INFO[04-22|12:19:42]  - u 0 165536 65536 
INFO[04-22|12:19:42]  - g 0 165536 65536 
WARN[04-22|12:19:42] CGroup memory swap accounting is disabled, swap limits will be ignored. 
INFO[04-22|12:19:42] Kernel features: 
INFO[04-22|12:19:42]  - netnsid-based network retrieval: no 
INFO[04-22|12:19:42]  - unprivileged file capabilities: yes 
INFO[04-22|12:19:42] Initializing local database 
DBUG[04-22|12:19:42] Initializing database gateway 
DBUG[04-22|12:19:42] Connecting to a local LXD over a Unix socket 
DBUG[04-22|12:19:42] Sending request to LXD                   method=GET url=http://unix.socket/1.0 etag=
DBUG[04-22|12:19:42] Detected stale unix socket, deleting 
INFO[04-22|12:19:42] Starting /dev/lxd handler: 
INFO[04-22|12:19:42]  - binding devlxd socket                 socket=/var/lib/lxd/devlxd/sock
INFO[04-22|12:19:42] REST API daemon: 
INFO[04-22|12:19:42]  - binding Unix socket                   socket=/var/lib/lxd/unix.socket
INFO[04-22|12:19:42]  - binding TCP socket                    socket=[::]:8443
INFO[04-22|12:19:42] Initializing global database 
DBUG[04-22|12:19:42] Found cert                               k=0
DBUG[04-22|12:19:42] Dqlite: server connection failed err=failed to establish network connection: some nodes are behind this node's version address=192.168.201.11:8443 attempt=0 
DBUG[04-22|12:19:42] Dqlite: connected address=192.168.201.12:8443 attempt=0 
DBUG[04-22|12:19:42] Database error: failed to update node version info: updated 0 rows instead of 1 
EROR[04-22|12:19:42] Failed to start the daemon: failed to open cluster database: failed to ensure schema: failed to update node version info: updated 0 rows instead of 1 
INFO[04-22|12:19:42] Starting shutdown sequence 
INFO[04-22|12:19:42] Stopping REST API handler: 
INFO[04-22|12:19:42]  - closing socket                        socket=[::]:8443
INFO[04-22|12:19:42]  - closing socket                        socket=/var/lib/lxd/unix.socket
INFO[04-22|12:19:42] Stopping /dev/lxd handler 
INFO[04-22|12:19:42]  - closing socket                        socket=/var/lib/lxd/devlxd/sock
DBUG[04-22|12:19:42] Stop database gateway 
INFO[04-22|12:19:42] Stopping REST API handler: 
INFO[04-22|12:19:42] Stopping /dev/lxd handler 
INFO[04-22|12:19:42] Stopping REST API handler: 
INFO[04-22|12:19:42] Stopping /dev/lxd handler 
DBUG[04-22|12:19:42] Not unmounting temporary filesystems (containers are still running) 
INFO[04-22|12:19:42] Saving simplestreams cache 
INFO[04-22|12:19:42] Saved simplestreams cache 
Error: failed to open cluster database: failed to ensure schema: failed to update node version info: updated 0 rows instead of 1
sysop@kvmnode1:~$ 

Any hint?

I've found 2 charms relative to "The charmed distribution of kubernetes".

The first at https://jujucharms.com/canonical-kubernetes/ seems to have only the necessary components.

The second at https://jujucharms.com/canonical-kubernetes/2 adds topbeat filebeat elastic search and kibana.

Strangely the two charms say they are installed with the command "juju deploy canonical-kubernetes"

So my questions:

• what is the correct charm?
• what charm will be installed with the command "juju deploy canonical-kubernetes"?

Thanks

UPDATE 2

Top posting because it is needed to apply the suggested solution.

Found on second answer to this question: Can netplan configured nameservers supersede (not merge with) the DHCP nameservers:

This has been fixed in the netplan repository on github, and will presumably make its way into Ubuntu at some point.

Two new options have been added, dhcp4-overrides and dhcp6-overrides. To ignore DNS servers from DHCP you would do something like

Anyone knows how to update netplan in Ubuntu 18.04?

Original question

I have an LXD vm with 2 network interfaces. If I use Ubuntu 16.04 (interfaces) I have 1 default gateway. If I use Ubuntu 18.04 (netplan) I have 2 default gateways. How can I get rid of the second gateway?

Ubuntu 16.04 configuration:

root@servizi:/etc/network/interfaces.d# ls -lha
total 3.5K
drwxr-xr-x 2 root root   4 Jul 31  2017 .
drwxr-xr-x 7 root root   8 Jul 12  2017 ..
-rw-r--r-- 1 root root 367 Jul 30  2017 50-cloud-init.cfg
-rw-r--r-- 1 root root  97 Jul 31  2017 60-locale.cfg
root@servizi:/etc/network/interfaces.d# cat 50-cloud-init.cfg 
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
root@servizi:/etc/network/interfaces.d# cat 60-locale.cfg 
auto eth1
iface eth1 inet dhcp
        up route add -net 192.168.99.0 netmask 255.255.255.0 gw 10.0.1.1
root@servizi:/etc/network/interfaces.d# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.220.90.1     0.0.0.0         UG    0      0        0 eth0
10.0.1.0        0.0.0.0         255.255.255.0   U     0      0        0 eth1
10.220.90.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.99.0    10.0.1.1        255.255.255.0   UG    0      0        0 eth1
root@servizi:/etc/network/interfaces.d# 

Ubuntu 18.04 configuration

root@servizi2:/etc/netplan# ls -lh
total 2.0K
-rw-r--r-- 1 root root 381 Jan 24 17:30 50-cloud-init.yaml
-rw-r--r-- 1 root root 177 Feb  1 20:25 60-locale.yaml
root@servizi2:/etc/netplan# cat 50-cloud-init.yaml 
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    ethernets:
        eth0:
            dhcp4: true
root@servizi2:/etc/netplan# cat 60-locale.yaml 
# seconda scheda
network:
    version: 2
    ethernets:
        eth1:
            dhcp4: true
            routes:
            - to: 192.168.99.0/24
            via: 10.0.1.1

root@servizi2:/etc/netplan# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.220.90.1     0.0.0.0         UG    100    0        0 eth0
0.0.0.0         10.0.1.1        0.0.0.0         UG    100    0        0 eth1
10.0.1.0        0.0.0.0         255.255.255.0   U     0      0        0 eth1
10.0.1.1        0.0.0.0         255.255.255.255 UH    100    0        0 eth1
10.220.90.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
10.220.90.1     0.0.0.0         255.255.255.255 UH    100    0        0 eth0
root@servizi2:/etc/netplan#

UPDATE

Tried what @slangasek suggested and the second file is now:

root@servizi2:/etc/netplan# cat 60-locale.yaml 
# seconda scheda
network:
    version: 2
    ethernets:
        eth1:
            dhcp4: true
            dhcp4-overrides:
                    use-routes: false
            routes:
                - to: 192.168.99.0/24
                  via: 10.0.1.1

But netplan try gives the error "unknown key dhcp4-overrides"

root@servizi2:/etc/netplan# netplan try
Error in network definition /etc/netplan/60-locale.yaml line 5 column 12: unknown key dhcp4-overrides

An error occurred: the configuration could not be generated

Reverting.
root@servizi2:/etc/netplan#

Wha can I do?

I have a host machine (KVM with Kubuntu 18.04) with a LXD guest (based on ubuntu18.04 image).

I can ssh from guest to host.

But trying to ssh from host to guest gives an

Permission denied (publickey)

error

Step to reproduce:

• lxc exec into the guest
• exec login with ubuntu user (to avoid root permissions problems)
• ssh to host - SUCCESS
• exit form user ubuntu - exit from guest
• from host ssh into ubuntu@guest - ERROR

What I'm doing wrong?

Below the complete session transcript

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:~$ 

I have:

• host: Kubuntu 18.04 fresh install + kvm + virt-manager
• guest: Kubuntu 18.04 fresh install

I plug an external drive in host and it is visible in sudo lsusb

In virt-manager for a vm I select the disk from the menu "virtual machine" -> "USB device redirection" popup window.

The disk is visible and selectable.

But inside the VM the disk is not visible also sudo lsusb do not show any disk

Tried the operations with the VM turned off and the VM turned on: nothing changes

What can I do?

I'm trying to format a disk but whatever I try after a reboot the old partition is always there.

I tried to see the partition with fdisk and format again using mkfs.ext4

    mirto@mirto-C35:~$ sudo fdisk /dev/sdb

    Welcome to fdisk (util-linux 2.31.1).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.


    Comando (m per richiamare la guida): p
    Disk /dev/sdb: 238,5 GiB, 256060514304 bytes, 500118192 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x7f633251

    Dispositivo Avvio Start      Fine   Settori   Size Id Tipo
    /dev/sdb1          2048 500117503 500115456 238,5G 83 Linux

    Comando (m per richiamare la guida): q

    mirto@mirto-C35:~$ sudo mkfs.ext4 -F -F /dev/sdb1
    mke2fs 1.44.1 (24-Mar-2018)
    Creazione del file system con 62514432 4k blocchi e 15630336 inode
    Etichetta del file system=c0a5c02e-4c6c-42f4-88c9-70ba4a198346
    Backup del superblocco salvati nei blocchi: 
            32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
            4096000, 7962624, 11239424, 20480000, 23887872

    Allocating group tables: fatto                            
    Scrittura delle tavole degli inode: fatto                            
    Creating journal (262144 blocks): fatto
    Scrittura delle informazioni dei super-blocchi e dell'accounting del file system:  

The command enter a continous loop trying to write the super-bloks and in syslog I see:

    May  6 10:19:10 mirto-C35 kernel: [ 3778.053676] ata5.00: failed command: WRITE DMA EXT
    May  6 10:19:10 mirto-C35 kernel: [ 3778.053694] ata5.00: cmd 35/00:40:70:22:dd/00:05:0e:00:00/e0 tag 28 dma 688128 out
    May  6 10:19:10 mirto-C35 kernel: [ 3778.053694]          res 51/04:40:70:22:dd/00:05:0e:00:00/e0 Emask 0x1 (device error)
    May  6 10:19:10 mirto-C35 kernel: [ 3778.053703] ata5.00: status: { DRDY ERR }
    May  6 10:19:10 mirto-C35 kernel: [ 3778.053709] ata5.00: error: { ABRT }
    May  6 10:19:10 mirto-C35 kernel: [ 3778.139798] ata5.00: configured for UDMA/33
    May  6 10:19:10 mirto-C35 kernel: [ 3778.139816] ata5: EH complete
    May  6 10:19:10 mirto-C35 kernel: [ 3778.153651] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
    May  6 10:19:10 mirto-C35 kernel: [ 3778.153660] ata5.00: irq_stat 0x40000001
    May  6 10:19:10 mirto-C35 kernel: [ 3778.153670] ata5.00: failed command: WRITE DMA EXT
    May  6 10:19:10 mirto-C35 kernel: [ 3778.153685] ata5.00: cmd 35/00:40:70:22:dd/00:05:0e:00:00/e0 tag 30 dma 688128 out
    May  6 10:19:10 mirto-C35 kernel: [ 3778.153685]          res 51/04:40:70:22:dd/00:05:0e:00:00/e0 Emask 0x1 (device error)
    May  6 10:19:10 mirto-C35 kernel: [ 3778.153693] ata5.00: status: { DRDY ERR }
    May  6 10:19:10 mirto-C35 kernel: [ 3778.153698] ata5.00: error: { ABRT }
    May  6 10:19:10 mirto-C35 kernel: [ 3778.238259] ata5.00: configured for UDMA/33
    May  6 10:19:10 mirto-C35 kernel: [ 3778.238280] sd 4:0:0:0: [sdb] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    May  6 10:19:10 mirto-C35 kernel: [ 3778.238282] sd 4:0:0:0: [sdb] tag#30 Sense Key : Illegal Request [current] 
    May  6 10:19:10 mirto-C35 kernel: [ 3778.238284] sd 4:0:0:0: [sdb] tag#30 Add. Sense: Unaligned write command
    May  6 10:19:10 mirto-C35 kernel: [ 3778.238286] sd 4:0:0:0: [sdb] tag#30 CDB: Write(10) 2a 00 0e dd 22 70 00 05 40 00
    May  6 10:19:10 mirto-C35 kernel: [ 3778.238287] print_req_error: I/O error, dev sdb, sector 249373296
    May  6 10:19:10 mirto-C35 kernel: [ 3778.238387] ata5: EH complete
    May  6 10:19:10 mirto-C35 kernel: [ 3778.273636] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
    May  6 10:19:10 mirto-C35 kernel: [ 3778.273641] ata5.00: irq_stat 0x40000001
    May  6 10:19:10 mirto-C35 kernel: [ 3778.273645] ata5.00: failed command: WRITE DMA EXT
    May  6 10:19:10 mirto-C35 kernel: [ 3778.273652] ata5.00: cmd 35/00:40:b0:27:dd/00:05:0e:00:00/e0 tag 2 dma 688128 out
    May  6 10:19:10 mirto-C35 kernel: [ 3778.273652]          res 51/04:40:b0:27:dd/00:05:0e:00:00/e0 Emask 0x1 (device error)
    May  6 10:19:10 mirto-C35 kernel: [ 3778.273655] ata5.00: status: { DRDY ERR }
    May  6 10:19:10 mirto-C35 kernel: [ 3778.273657] ata5.00: error: { ABRT }
    May  6 10:19:10 mirto-C35 kernel: [ 3778.328424] ata5.00: configured for UDMA/33
    May  6 10:19:10 mirto-C35 kernel: [ 3778.328436] ata5: EH complete
    May  6 10:19:10 mirto-C35 kernel: [ 3778.353667] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
    May  6 10:19:10 mirto-C35 kernel: [ 3778.353672] ata5.00: irq_stat 0x40000001
    May  6 10:19:10 mirto-C35 kernel: [ 3778.353675] ata5.00: failed command: WRITE DMA EXT
    May  6 10:19:10 mirto-C35 kernel: [ 3778.353682] ata5.00: cmd 35/00:40:b0:27:dd/00:05:0e:00:00/e0 tag 4 dma 688128 out
    May  6 10:19:10 mirto-C35 kernel: [ 3778.353682]          res 51/04:40:b0:27:dd/00:05:0e:00:00/e0 Emask 0x1 (device error)
    May  6 10:19:10 mirto-C35 kernel: [ 3778.353685] ata5.00: status: { DRDY ERR }
    May  6 10:19:10 mirto-C35 kernel: [ 3778.353687] ata5.00: error: { ABRT }
    May  6 10:19:10 mirto-C35 kernel: [ 3778.457184] ata5.00: configured for UDMA/33
    May  6 10:19:10 mirto-C35 kernel: [ 3778.457198] ata5: EH complete

Seems that the disk is protected and I cannot write on it.

How can I clear this disk?

UPDATE

The disk is a Plextor SSD

PLEXTOR PX-256M6G-2280

The output of hdparm is

    mirto@mirto-C35:~$ sudo hdparm -I /dev/sdb
    [sudo] password di mirto: 

    /dev/sdb:

    ATA device, with non-removable media
            Model Number:       PLEXTOR PX-256M6G-2280                  
            Serial Number:      P02439111419        
            Firmware Revision:  1.00    
            Transport:          Serial, ATA8-AST, SATA II Extensions, SATA Rev 2.6, SATA Rev 3.0
    Standards:
            Used: ATA/ATAPI-7 T13 1532D revision 4a 
            Supported: 8 7 6 5 & some of 8
    Configuration:
            Logical         max     current
            cylinders       16383   16383
            heads           16      16
            sectors/track   63      63
            --
            CHS current addressable sectors:    16514064
            LBA    user addressable sectors:   268435455
            LBA48  user addressable sectors:   500118192
            Logical  Sector size:                   512 bytes
            Physical Sector size:                   512 bytes
            Logical Sector-0 offset:                  0 bytes
            device size with M = 1024*1024:      244198 MBytes
            device size with M = 1000*1000:      256060 MBytes (256 GB)
            cache/buffer size  = unknown
            Nominal Media Rotation Rate: Solid State Device
    Capabilities:
            LBA, IORDY(can be disabled)
            Queue depth: 32
            Standby timer values: spec'd by Standard, no device specific minimum
            R/W multiple sector transfer: Max = 16  Current = 16
            DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
                Cycle time: min=120ns recommended=120ns
            PIO: pio0 pio1 pio2 pio3 pio4 
                Cycle time: no flow control=120ns  IORDY flow control=120ns
    Commands/features:                                                                                                                                                                                                 
            Enabled Supported:                                                                                                                                                                                         
            *    SMART feature set                                                                                                                                                                                  
                    Security Mode feature set                                                                                                                                                                          
            *    Power Management feature set                                                                                                                                                                       
            *    Write cache                                                                                                                                                                                        
            *    Look-ahead
            *    Host Protected Area feature set
            *    WRITE_BUFFER command
            *    READ_BUFFER command
            *    DOWNLOAD_MICROCODE
                    SET_MAX security extension
            *    48-bit Address feature set
            *    Device Configuration Overlay feature set
            *    Mandatory FLUSH_CACHE
            *    FLUSH_CACHE_EXT
            *    SMART error logging
            *    SMART self-test
            *    General Purpose Logging feature set
            *    64-bit World wide name
            *    Segmented DOWNLOAD_MICROCODE
            *    Gen1 signaling speed (1.5Gb/s)
            *    Gen2 signaling speed (3.0Gb/s)
            *    Gen3 signaling speed (6.0Gb/s)
            *    Native Command Queueing (NCQ)
            *    Host-initiated interface power management
            *    Phy event counters
            *    DMA Setup Auto-Activate optimization
                    Device-initiated interface power management
            *    Software settings preservation
                    Device Sleep (DEVSLP)
            *    SMART Command Transport (SCT) feature set
            *    SCT Write Same (AC2)
            *    SCT Error Recovery Control (AC3)
            *    SCT Features Control (AC4)
            *    SCT Data Tables (AC5)
            *    Data Set Management TRIM supported (limit 8 blocks)
    Security: 
                    supported
            not     enabled
            not     locked
                    frozen
            not     expired: security count
                    supported: enhanced erase
            6min for SECURITY ERASE UNIT. 6min for ENHANCED SECURITY ERASE UNIT.
    Logical Unit WWN Device Identifier: 50023031002d3f41
            NAA             : 5
            IEEE OUI        : 002303
            Unique ID       : 1002d3f41
    Device Sleep:
            DEVSLP Exit Timeout (DETO): 100 ms (drive)
            Minimum DEVSLP Assertion Time (MDAT): 10 ms (drive)
    Checksum: correct
    mirto@mirto-C35:~$ 

I created a Ubuntu container

lxc launch ubuntu images:ubuntu/xenial mycontainer

I can access the container using

lxc exec mycontainer bash

I found mysel logged in as root without asking any password

I see that there is a "ubuntu" user defined

How can I access a software installed in the container (e.g. webmin) which asks for a username and password?

What are the default passwords?

I'm trying to bootstrap juju on a virtualbox machine with ubuntu 16.04 using lxd cloud obtainig the error

ERROR Get https://10.229.0.1:8443/1.0: Gateway Time-out

Snap says:

sysop@ubuntu01:~$ sudo snap list
[sudo] password for sysop: 
Name  Version  Rev   Developer  Notes
core  16-2     1689  canonical  -
juju  2.2.0    1956  canonical  classic
lxd   2.14     2417  canonical  -

LXC is working correctly and I have a container delivered. lxc list says:

sysop@ubuntu01:~$ lxc list --verbose
+-------+---------+--------------------+------+------------+-----------+
| NAME  |  STATE  |        IPV4        | IPV6 |    TYPE    | SNAPSHOTS |
+-------+---------+--------------------+------+------------+-----------+
| primo | RUNNING | 10.229.0.73 (eth0) |      | PERSISTENT | 0         |
+-------+---------+--------------------+------+------------+-----------+

I'm behind a proxy that requires authentication so in lxc info I have:

sysop@ubuntu01:~$ lxc info
config:
   core.https_address: '[::]'
   core.proxy_http: http://user:password@proxy-address:8080/
   core.proxy_https: http://user:password@proxy-address:8080/
   core.proxy_ignore_hosts: localhost

The output of juju bootstrap is:

    sysop@ubuntu01:~$ juju bootstrap localhost lxd1 --debug
    09:34:53 INFO  juju.cmd supercommand.go:63 running juju [2.2.0 gc go1.8]
    09:34:53 DEBUG juju.cmd supercommand.go:64   args: []string{"/snap/juju/1956/bin/juju", "bootstrap", "localhost", "lxd1", "--debug"}
    09:34:53 DEBUG juju.tools.lxdclient client.go:230 connecting to LXD remote "local": "unix:///var/snap/lxd/common/lxd/unix.socket"
    09:34:54 INFO  juju.tools.lxdclient client.go:284 using LXD API version "1.0"
    09:34:54 INFO  juju.tools.lxdclient client.go:333 LXD "default" profile uses network bridge "lxdbr0"
    09:34:54 INFO  cmd provider.go:179 Resolved LXD host address on bridge lxdbr0: 10.229.0.1:8443
    09:34:54 INFO  cmd cloudcredential.go:51 no credentials found, checking environment
    09:34:54 DEBUG juju.tools.lxdclient client.go:230 connecting to LXD remote "local": "unix:///var/snap/lxd/common/lxd/unix.socket"
    09:34:54 INFO  juju.tools.lxdclient client.go:284 using LXD API version "1.0"
    09:34:54 INFO  juju.tools.lxdclient client.go:333 LXD "default" profile uses network bridge "lxdbr0"
    09:34:54 DEBUG juju.cmd.juju.commands bootstrap.go:803 authenticating with region "" and credential "localhost" (LXD credential "localhost")
    09:34:54 DEBUG juju.cmd.juju.commands bootstrap.go:915 provider attrs: map[]
    09:34:54 INFO  cmd authkeys.go:114 Adding contents of "/home/sysop/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
    09:34:54 INFO  cmd authkeys.go:114 Adding contents of "/home/sysop/.ssh/id_rsa.pub" to authorized-keys
    09:34:54 DEBUG juju.cmd.juju.commands bootstrap.go:971 preparing controller with config: map[net-bond-reconfigure-delay:17 disable-network-management:false authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCpLnUIrvGmeOMKaH0KLltB94Hn20c4ARM6/vSW6PguUr04+EzU2q9s/GFiIq7VjC0aWxQydDJG/4HqThf0VX5nB9h5sYBLIaq8LoMemw/FtsZrnQ2En3u9kngvcYkRmQEcyCzdHmhzVKG1JAE3NYz67aCaa2OAWZw7fDcXP78KsYDuSv8eTFr4qPoGGi2ayG/NeXkM8WgS8fgQI9emOn9zFVrHIo7Ah2Wa9ucUJjXQvNA+6hZjM2DnxeLV4gdVLxLBvxF1Vj9MHqArPBUZ4ZEFGcdXYoPyny2S6iT3vf3fbCaU785JNweCQwZ0oxRXCDYWXPhGY4zVwzUK1ykojOrh juju-client-key
    ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCjq011k7jLFei5RL7m07dDwEHA4hoKI9AN/WlfjH+ThrUErSV4vG3SRL3jClUldirTTLeT3XwwiGMpLAfxtamI/cbFjuqCY7nHJ+zgQ+GfmgpMfulYxJgz9D1oGdL8+Mn3EfG5V4pfDe1uTiOkmKkChh53rWTznAuDQYbFaXlbQdsVbUDRjmhuAjKnPqX/81WKeB4XedNAsycsqhBmK2ITx22ff2PwkHaegsGUzbXcRVY8i47gq96vCU3gLb64fUkTA9miEAovtpalsr13jSbzTrLfwtExVbpew0EAb4de5BqQATqOtexD6CNzkxEzmHp7am0c8MdzMjBFpkCIN29/ sysop@ubuntu01
    automatically-retry-hooks:true agent-metadata-url: type:lxd ignore-machine-addresses:false proxy-ssh:false image-stream:released enable-os-upgrade:true apt-ftp-proxy: ftp-proxy: http-proxy: transmit-vendor-metrics:true name:controller apt-https-proxy: firewall-mode:instance logforward-enabled:false default-series:xenial max-status-history-age:336h ssl-hostname-verification:true no-proxy:127.0.0.1,localhost,::1 apt-mirror: https-proxy: max-status-history-size:5G apt-no-proxy: resource-tags: apt-http-proxy: logging-config: agent-stream:released uuid:2168b6e8-f8b8-4edb-8982-191e4b407901 test-mode:false provisioner-harvest-mode:destroyed image-metadata-url: development:false enable-os-refresh-update:true]
    09:34:54 DEBUG juju.tools.lxdclient client.go:230 connecting to LXD remote "remote": "10.229.0.1:8443"
    ERROR Get https://10.229.0.1:8443/1.0: Gateway Time-out
    09:34:54 DEBUG cmd supercommand.go:459 error stack: 
    Get https://10.229.0.1:8443/1.0: Gateway Time-out
    github.com/juju/juju/tools/lxdclient/client.go:278: 
    github.com/juju/juju/tools/lxdclient/client.go:132: 
    github.com/juju/juju/provider/lxd/environ_raw.go:92: 
    github.com/juju/juju/provider/lxd/environ.go:67: 
    github.com/juju/juju/provider/lxd/provider.go:57: 
    github.com/juju/juju/environs/bootstrap/prepare.go:160: 
    github.com/juju/juju/environs/bootstrap/prepare.go:99: 
    github.com/juju/juju/cmd/juju/commands/bootstrap.go:450: 

What can I do to bootstrap JUJU?

UPDATE:

Tried everything suggested in this thread: Juju 2.0 proxy for bootstrap

--model-defaults is undefined for juju 2.2.0

--config is simply ignored

sysop@ubuntu01:~$ juju bootstrap lxd --model-defaults=config.yaml ERROR flag provided but not defined: --model-defaults sysop@ubuntu01:~$ juju bootstrap lxd --config=config.yaml ERROR Get https://10.229.0.1:8443/1.0: Gateway Time-out

I don't know what else to try. Any suggestion?

One step ahead.

Setting the core.http_address to the lxdbr0 address and core.proxy_ignore_hosts to the same address the bootstrap process starts and create the lxc controller container but end in error saying:

09:30:29 ERROR juju.cmd.juju.commands bootstrap.go:492 unable to contact api server after 1 attempts: unable to connect to API: malformed HTTP response "\x15\x03\x01\x00\x02\x02\x16"

Then the process ends cleaning up the created container.

What can I do?

Lxc info says:

    sysop@ubuntu01:~$ lxc info
    config:
    core.https_address: 10.229.0.1:9000
    core.https_allowed_credentials: "true"
    core.https_allowed_headers: Origin, X-Requested-With, Content-Type, Accept
    core.https_allowed_methods: GET, POST, PUT, DELETE, OPTIONS
    core.https_allowed_origin: https://localhost:8000
    core.proxy_http: http://username:password@proxy:8080/
    core.proxy_https: http://username:password@proxy:8080/
    core.proxy_ignore_hosts: 10.229.0.1

config.yaml contains:

    default-series: xenial
    no-proxy: 10.229.0.1
    apt-http-proxy: http://username:password@proxy:8080
    apt-https-proxy: http://username:password@proxy:8080
    apt-ftp-proxy: http://username:password@proxy:8080
    http-proxy: http://username:password@proxy:8080
    https-proxy: http://username:password@proxy:8080
    ftp-proxy: http://username:password@proxy:8080

and the bootstrap log is:

    sysop@ubuntu01:~$ juju bootstrap localhost --config config.yaml --debug
    09:09:10 INFO  juju.cmd supercommand.go:63 running juju [2.2.0 gc go1.8]
    09:09:10 DEBUG juju.cmd supercommand.go:64   args: []string{"/snap/juju/1956/bin/juju", "bootstrap", "localhost", "--config", "config.yaml", "--debug"}
    09:09:10 DEBUG juju.tools.lxdclient client.go:230 connecting to LXD remote "local": "unix:///var/snap/lxd/common/lxd/unix.socket"
    09:09:10 INFO  juju.tools.lxdclient client.go:284 using LXD API version "1.0"
    09:09:10 INFO  juju.tools.lxdclient client.go:333 LXD "default" profile uses network bridge "lxdbr0"
    09:09:10 INFO  cmd provider.go:179 Resolved LXD host address on bridge lxdbr0: 10.229.0.1:9000
    09:09:10 INFO  cmd cloudcredential.go:51 no credentials found, checking environment
    09:09:10 DEBUG juju.tools.lxdclient client.go:230 connecting to LXD remote "local": "unix:///var/snap/lxd/common/lxd/unix.socket"
    09:09:10 INFO  juju.tools.lxdclient client.go:284 using LXD API version "1.0"
    09:09:10 INFO  juju.tools.lxdclient client.go:333 LXD "default" profile uses network bridge "lxdbr0"
    09:09:10 DEBUG juju.cmd.juju.commands bootstrap.go:803 authenticating with region "" and credential "localhost" (LXD credential "localhost")
    09:09:10 DEBUG juju.cmd.juju.commands bootstrap.go:915 provider attrs: map[]
    09:09:11 INFO  cmd authkeys.go:114 Adding contents of "/home/sysop/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
    09:09:11 INFO  cmd authkeys.go:114 Adding contents of "/home/sysop/.ssh/id_rsa.pub" to authorized-keys
    09:09:11 DEBUG juju.cmd.juju.commands bootstrap.go:971 preparing controller with config: map[logging-config: authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCpLnUIrvGmeOMKaH0KLltB94Hn20c4ARM6/vSW6PguUr04+EzU2q9s/GFiIq7VjC0aWxQydDJG/4HqThf0VX5nB9h5sYBLIaq8LoMemw/FtsZrnQ2En3u9kngvcYkRmQEcyCzdHmhzVKG1JAE3NYz67aCaa2OAWZw7fDcXP78KsYDuSv8eTFr4qPoGGi2ayG/NeXkM8WgS8fgQI9emOn9zFVrHIo7Ah2Wa9ucUJjXQvNA+6hZjM2DnxeLV4gdVLxLBvxF1Vj9MHqArPBUZ4ZEFGcdXYoPyny2S6iT3vf3fbCaU785JNweCQwZ0oxRXCDYWXPhGY4zVwzUK1ykojOrh juju-client-key
    ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCjq011k7jLFei5RL7m07dDwEHA4hoKI9AN/WlfjH+ThrUErSV4vG3SRL3jClUldirTTLeT3XwwiGMpLAfxtamI/cbFjuqCY7nHJ+zgQ+GfmgpMfulYxJgz9D1oGdL8+Mn3EfG5V4pfDe1uTiOkmKkChh53rWTznAuDQYbFaXlbQdsVbUDRjmhuAjKnPqX/81WKeB4XedNAsycsqhBmK2ITx22ff2PwkHaegsGUzbXcRVY8i47gq96vCU3gLb64fUkTA9miEAovtpalsr13jSbzTrLfwtExVbpew0EAb4de5BqQATqOtexD6CNzkxEzmHp7am0c8MdzMjBFpkCIN29/ sysop@ubuntu01
    max-status-history-age:336h enable-os-upgrade:true test-mode:false firewall-mode:instance image-metadata-url: image-stream:released ftp-proxy:http://username:password@proxy:8080 agent-stream:released name:controller development:false agent-metadata-url: resource-tags: transmit-vendor-metrics:true http-proxy:http://username:password@proxy:8080 max-status-history-size:5G apt-no-proxy: apt-mirror: net-bond-reconfigure-delay:17 apt-http-proxy:http://username:password@proxy:8080 default-series:xenial type:lxd logforward-enabled:false enable-os-refresh-update:true apt-https-proxy:http://username:password@proxy:8080 provisioner-harvest-mode:destroyed uuid:dc69de65-706c-4839-8456-b3afc7dce7f9 proxy-ssh:false automatically-retry-hooks:true ssl-hostname-verification:true no-proxy:10.229.0.1 apt-ftp-proxy:http://username:password@proxy:8080 disable-network-management:false https-proxy:http://username:password@proxy:8080 ignore-machine-addresses:false]
    09:09:11 DEBUG juju.tools.lxdclient client.go:230 connecting to LXD remote "remote": "10.229.0.1:9000"
    09:09:11 INFO  juju.tools.lxdclient client.go:284 using LXD API version "1.0"
    09:09:11 INFO  cmd bootstrap.go:481 Creating Juju controller "localhost-localhost" on localhost/localhost
    09:09:11 INFO  juju.cmd.juju.commands bootstrap.go:536 combined bootstrap constraints: 
    09:09:11 DEBUG juju.environs.bootstrap bootstrap.go:199 model "controller" supports service/machine networks: false
    09:09:11 DEBUG juju.environs.bootstrap bootstrap.go:201 network management by juju enabled: true
    09:09:11 INFO  cmd bootstrap.go:233 Loading image metadata
    09:09:11 INFO  cmd bootstrap.go:296 Looking for packaged Juju agent version 2.2.0 for amd64
    09:09:11 INFO  juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.2.0
    09:09:11 INFO  juju.environs.tools tools.go:101 finding agent binaries in stream "released"
    09:09:11 INFO  juju.environs.tools tools.go:103 reading agent binaries with major.minor version 2.2
    09:09:11 INFO  juju.environs.tools tools.go:111 filtering agent binaries by version: 2.2.0
    09:09:11 INFO  juju.environs.tools tools.go:117 filtering agent binaries by architecture: amd64
    09:09:11 DEBUG juju.environs.tools urls.go:109 trying datasource "keystone catalog"
    09:09:12 DEBUG juju.environs.simplestreams simplestreams.go:683 using default candidate for content id "com.ubuntu.juju:released:tools" are {20161007 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}
    09:09:14 INFO  juju.environs.bootstrap tools.go:74 found 15 packaged agent binaries
    09:09:14 INFO  cmd bootstrap.go:357 Starting new instance for initial controller
    09:09:14 INFO  cmd environ.go:152 To configure your system to better support LXD containers, please see: https://github.com/lxc/lxd/blob/master/doc/production-setup.md
    Launching controller instance(s) on localhost/localhost...
    09:09:14 DEBUG juju.provider.lxd environ_broker.go:40 StartInstance: "0", xenial
    09:09:14 DEBUG juju.cloudconfig.instancecfg instancecfg.go:825 Setting numa ctl preference to false
    09:09:14 DEBUG juju.environs imagemetadata.go:112 obtained image datasource "default cloud images"
    09:09:14 DEBUG juju.environs imagemetadata.go:112 obtained image datasource "default ubuntu cloud images"
    09:09:14 DEBUG juju.provider.lxd environ_broker.go:112 LXD requires https://, using: https://cloud-images.ubuntu.com/releases/
    09:09:14 DEBUG juju.tools.lxdclient client.go:230 connecting to LXD remote "default cloud images": "https://streams.canonical.com/juju/images/releases/"
    09:09:14 INFO  juju.tools.lxdclient client_image.go:166 no image for juju/xenial/amd64 found in https://streams.canonical.com/juju/images/releases/
    09:09:14 DEBUG juju.tools.lxdclient client.go:230 connecting to LXD remote "default ubuntu cloud images": "https://cloud-images.ubuntu.com/releases/"
    09:09:15 INFO  juju.tools.lxdclient client_image.go:170 found image from https://cloud-images.ubuntu.com/releases/ for juju/xenial/amd64 = 7a7ff654cbd8f5f09bec03aa19d8d7d92649127d18659036a963b1ea63f90d25
    09:09:17 INFO  juju.tools.lxdclient client_image.go:182 copying image for juju/xenial/amd64 from https://cloud-images.ubuntu.com/releases/: metadata: 100% (1.62GB/s)
    09:09:20 INFO  juju.tools.lxdclient client_image.go:182 copying image for juju/xenial/amd64 from https://cloud-images.ubuntu.com/releases/: rootfs: 1% (548.63kB/s)
    [...snip...]
    09:15:13 INFO  juju.tools.lxdclient client_image.go:182 copying image for juju/xenial/amd64 from https://cloud-images.ubuntu.com/releases/: rootfs: 99% (436.00kB/s)
    09:15:16 INFO  juju.tools.lxdclient client_image.go:182 copying image for juju/xenial/amd64 from https://cloud-images.ubuntu.com/releases/: rootfs: 100% (435.60kB/s)
    09:15:19 DEBUG juju.tools.lxdclient client_image.go:174 dropped 0 progress messagess/: rootfs: 100% (435.60kB/s)
    09:15:19 DEBUG juju.service discovery.go:63 discovered init system "systemd" from series "xenial"               
    09:15:19 DEBUG juju.provider.lxd environ_broker.go:230 LXD user data; 3981 bytes
    09:15:19 INFO  juju.provider.lxd environ_broker.go:211 starting instance "juju-dce7f9-0" (image "juju/xenial/amd64")...
    09:16:08 INFO  juju.provider.lxd environ_broker.go:56 started instance "juju-dce7f9-0"                          
    - juju-dce7f9-0 (arch=amd64)          
    09:16:09 INFO  juju.environs.bootstrap bootstrap.go:601 newest version: 2.2.0
    09:16:09 INFO  juju.environs.bootstrap bootstrap.go:616 picked bootstrap agent binary version: 2.2.0
    09:16:09 INFO  juju.environs.bootstrap bootstrap.go:393 Installing Juju agent on bootstrap instance
    09:16:10 INFO  cmd bootstrap.go:480 Fetching Juju GUI 2.7.3
    09:16:10 DEBUG juju.cloudconfig.instancecfg instancecfg.go:825 Setting numa ctl preference to false
    Waiting for address
    Attempting to connect to 10.229.0.159:22
    09:16:36 DEBUG juju.provider.common bootstrap.go:497 connection attempt for 10.229.0.159 failed: /var/lib/juju/nonce.txt does not exist
    09:16:41 INFO  juju.cloudconfig userdatacfg_unix.go:410 Fetching agent: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/agent/2.2.0/juju-2.2.0-ubuntu-amd64.tgz]>
    09:20:29 INFO  cmd bootstrap.go:420 Bootstrap agent now started
    09:20:30 INFO  juju.juju api.go:308 API endpoints changed from [] to [10.229.0.159:17070]
    09:20:31 INFO  cmd controller.go:82 Contacting Juju controller at 10.229.0.159 to verify accessibility...
    09:20:31 INFO  juju.juju api.go:67 connecting to API addresses: [10.229.0.159:17070]
    09:30:29 DEBUG juju.api apiclient.go:806 error dialing websocket: malformed HTTP response "\x15\x03\x01\x00\x02\x02\x16"
    09:30:29 ERROR juju.cmd.juju.commands bootstrap.go:492 unable to contact api server after 1 attempts: unable to connect to API: malformed HTTP response "\x15\x03\x01\x00\x02\x02\x16"
    09:30:29 DEBUG juju.cmd.juju.commands bootstrap.go:493 (error details: [{github.com/juju/juju/cmd/juju/common/controller.go:115: unable to contact api server after 1 attempts} {github.com/juju/juju/cmd/juju/common/controller.go:39: } {github.com/juju/juju/juju/api.go:72: } {github.com/juju/juju/api/apiclient.go:190: } {github.com/juju/juju/api/apiclient.go:596: } {github.com/juju/juju/api/apiclient.go:711: } {github.com/juju/juju/api/apiclient.go:807: unable to connect to API} {github.com/juju/juju/api/apiclient.go:831: } {malformed HTTP response "\x15\x03\x01\x00\x02\x02\x16"}])
    09:30:29 DEBUG juju.cmd.juju.commands bootstrap.go:1078 cleaning up after failed bootstrap
    09:30:29 INFO  juju.provider.common destroy.go:20 destroying model "controller"
    09:30:29 INFO  juju.provider.common destroy.go:31 destroying instances
    09:30:41 INFO  juju.provider.common destroy.go:51 destroying storage
    09:30:41 DEBUG juju.provider.lxd environ.go:193 instances: []
    09:30:41 INFO  cmd supercommand.go:465 command finished
    sysop@ubuntu

Installing the Canonical distribution of Kubernetes removes the LXC zfs definition forcing writes to dir

Before conjure-up the "lxc info" command says: ...snip... config:  storage.zfs_pool_name: lxd apiextensions: - id_map apistatus: stable ...snip... serverversion: 2.0.9  storage: zfs  storageversion: "5"

After conjure-up completes correctly (I can see the kubernetes dashboard and the juju gui) the storage is forced to dir

The command "lxc info" says: ...snip... config: core.https_address: '[::]' storage.zfs_pool_name: lxd api_extensions: - storage_zfs_remove_snapshots - container_host_shutdown_timeout ...snip... server_pid: 5149 server_version: "2.11" storage: dir storage_version: "1"

and the zpool command says thar there was no read and no writes: sysop@vx07:~$ sudo zpool status [sudo] password di sysop: pool: lxd state: ONLINE scan: none requested config:

    NAME        STATE     READ WRITE CKSUM
    lxd         ONLINE       0     0     0
      vdb1      ONLINE       0     0     0

errors: No known data errors sysop@vx07:~$

What can I do to force conjure-up to use the zfs backend?

I successfully installed openstack nova-lxd on a kvm virtual machine using conjure-up.

After a VM shutdown; when I start the VM openstack doesn't start. lxc list shows one instance in "RUNNING" state and all the other in "STOPPED" state.

How can I start the other instances?

Using Kubuntu 14.10 64Bit, to reproduce

1. select Kubuntu 14.10 64bit ISO image
2. use a USB key of 8Gb or more (tried VARIOUS BRAND)
3. select erase disk
4. assign 4Gb for the persistent disk
5. start the operation

The progress stops when it says creating persistent file 99% From here nothing happens

I also posted as bug here: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1411539

Anyone is experiencing this problem?

I have 2 notebook that see all the wireless access point except one.

The computers are:

• HP Pavilion DV6 - wifi Broadcom BCM4312 - Kubuntu 13.10 64bit
• Asus EEEPC 1018P - wifi broadcom BMC4313 - Kubuntu 14.04 64 Bit Aplha 2

The missing access point is a D-Link DIR-615 set up with:

• mixed mode "Mixed 802.11n, 802.11g and 802.11b"
• auto channel scan enabled
• wireless channel CH13 (not changeable)

I have another AP and this one (a TP-Link) is correctly identified and used for connections.

All other devices I have in home (some Android smartphones and tablets, an iPad and a Playstation) correctly see and use the missing AP

Also the computers connets to this AP if booted with Windows.

I don't know in which Kubuntu version or update the problem arose, but I tried on the Asus a fresh install of 12.04.3, 12.10, 13.04, 13.10, 14.04Alpha2 and obtained the same result:

The driver in use is WL.
nm-tool on HP says

Device: eth1  [efm2] ---------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            wl
  State:             connected
  Default:           yes
  HW Address:        F0:7B:CB:95:14:08

  Capabilities:
    Speed:           54 Mb/s

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points (* = current AP)

    Telecom-64869841:Infra, A4:B1:E9:D3:B6:D1, Freq 2437 MHz, Rate 54 Mb/s, Strength 10 WPA WPA2
    BOX:             Infra, A0:F3:C1:98:58:80, Freq 2447 MHz, Rate 54 Mb/s, Strength 17 WPA2

    FASTWEB-1-c85NyZctS6gd: Infra, E0:91:53:4E:4C:58, Freq 2437 MHz, Rate 54 Mb/s, Strength 12 WPA

    *efm2:           Infra, F8:1A:67:30:A0:08, Freq 2412 MHz, Rate 54 Mb/s, Strength 66 WPA >WPA2

  IPv4 Settings:
    Address:         192.168.253.100
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.253.1

    DNS:             192.168.253.1

My AP are efm2 (listed) and efm (missing); all other AP are from neighbors

Followed the instructions in the first response.

I still see only the far AP and don't see the nearest DIR-615 AP.

nm-tool says:

- Device: wlan0 ----------------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            b43
  State:             disconnected
  Default:           no
  HW Address:        F0:7B:CB:95:14:08
  Capabilities:
  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes
  Wireless Access Points 
    efm2:            Infra, F8:1A:67:30:A0:08, Freq 2412 MHz, Rate 54 Mb/s, Strength 46 WPA >WPA2

What else can I try?

As in the comments, the iwlist command is

mirto@msb03:/etc/network$ sudo iwlist eth1 freq

eth1      26 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz
          Channel 12 : 2.467 GHz
          Channel 13 : 2.472 GHz
          Channel 14 : 2.484 GHz
          Channel 36 : 5.18 GHz
          Channel 38 : 5.19 GHz
          Channel 40 : 5.2 GHz
          Channel 42 : 5.21 GHz
          Channel 44 : 5.22 GHz
          Channel 46 : 5.23 GHz
          Channel 48 : 5.24 GHz
          Channel 149 : 5.745 GHz
          Channel 153 : 5.765 GHz
          Channel 157 : 5.785 GHz
          Channel 161 : 5.805 GHz
          Channel 165 : 5.825 GHz

At this point, I returned to the wl driver because I see no difference in behaviour

Following bug [wireless-tools] Cannot use channel 12 or 13 of wifi in a region where it is legal

I tried

mirto@msb03:/etc/network$ sudo cat /sys/module/cfg80211/parameters/ieee80211_regdom

00

That says 00 instead of US or EU

After googling bugs I found that there exist an /etc/defeult/crda file with an empty domain

ASAP I'll try to set the domain

sudo cat /etc/default/crda
  Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set
  the initial regulatory domain setting for IEEE 802.11 devices which operate
  on this system.

 Governments assert the right to regulate usage of radio spectrum within
 their respective territories so make sure you select a ISO/IEC 3166-1 alpha2
 country code suitable for your location or you may infringe on local
 legislature. See `/usr/share/zoneinfo/zone.tab' for a table of timezone
 descriptions containing ISO/IEC 3166-1 alpha2 country codes.

REGDOMAIN=

so I tried

REGDOMAIN=IT

but nothing changed

After setting IT in domain. I have:

$ sudo iw reg get
country IT:
        (2402 - 2482 @ 40), (N/A, 20)
        (5170 - 5250 @ 40), (N/A, 20)
        (5250 - 5330 @ 40), (N/A, 20), DFS
        (5490 - 5710 @ 40), (N/A, 27), DFS
        (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR

I tried on another computer to scan the missing AP:

• Abandoned again the wl driver for the b43 driver
• rebooted
• added the IT domain in /etc/default/crda

Now seems to work.

I'll try the same operation on the Asus that have a fresh install

_________ Solved on Asus ___________________________

Operations to solve the problem on Asus Kubuntu 14.04Alpha2

sudo apt-get remove --purge bcmwl-kernel-source sudo apt-get install linux-firmware-nonfree

reboot

reboot

add IT as domain in /etc/default/crda

REGDOMAIN=IT

reboot

reboot

______ last update _________________________

The drivers selected are:

on HP driver b43

on Asus driver brcmsmac

In Thunderbird 15.0 on Kubuntu 12.04 64Bit disappeared the folder list in the copy to menu

To reproduce

• select write (new message) appears a new window
• select options
• selcet copy to - appears a little white point instead of the folder list

Same problem on two different notebooks; one upgraded from 11.04 and the other with a clean 12.04 installation.

Seems related to the 15.0 version

See this question.

The FN keys are not working

Using answer in this question I installed the asus-wmi-dkms_0.2_all.deb.gz package

Now, using xev I see that the keys emit keycodes (for backlight keys xev says for fn-f3 and fn-f4 keycode 237)

But no keyboard backlight, also volume keys have no effect

================ original question ========================================

I cannot enable the keyboard backlight Seems that the leds class is missing I've not found the classes used in Keyboard light hotkey (Fn + F3 and F4) rarely work on an Asus G60J

Description of my framework:

===========================================================

Machine: Asus N56V laptop

===========================================================

Software

• Kubuntu 12.04 amd64

• kernel (3.5.0.5-generic) and drivers from xorg-edgers fresh X crack ppa

===========================================================

Hardware and problems

• after installation do not boot - SOLVED using boot-repair

• every couple of hours the system freezes - SOLVED using 3.5 kernel

• keybord FN keys - NOT WORKING

• Keyboard backlight - NOT WORKING

• Nvidia GEFORCE GT - NOT USED glxgears says 60 fps

• Ethernet Atheros card - SOLVED install alx driver

• external subwoofer - SOLVED adding options snd-hda-intel model=asus-mode4

==========================================================

Solutions

see the answers to the this and this question.

==========================================================

On a fresh installation of Kubuntu 12.04 amd64 on a Asus N56V jockey-kde says that there are no useful prprietary drivers.

Using the info-center I can see

in PCI an Nvidia Non-VGA unclassified device (0x00)

in Opengl an Intel Ivy Bridge Graphics Controller

=======================================================================

I've found that the 3.2 kernel is missing many kernel modules for the Asus N56V machine and other ivy-bridge machines.

The machine is also overheating.

I'm closing this thread and I'll start a new one after installing 12.10 alpha 2 that uses a 3.5 kernel

=======================================================================

SOLVED

I'm trying to install Kubuntu alogng with the preinstalled Windows 7.

I boot from CD Create three partititons: / (ext4), swap and a 100MB reserved bios

All installs correctly, but I'm not able to boot Kubuntu

From the bios setup disappeared the option to use legacy bios instead of UEFI (or at least I cannot find it)

I have the option to create a new boot entry, but I don't know what to type in.

What can I do?

Thanks Mirto

=========== added 10 Lug 18:54 ========================

Seems relate to bug 972122 ( https : // bugs.launchpad.net/ubuntu/+source/partman-efi/+bug/972122 ) The message I saw when the EFI boot partition was missing is the same reported in https : // launchpadlibrarian.net/99750202/EFI-warning.jpg

The bug is marked as fixed-released What I'm missing?

There is any particular install CD using partman-efi?

============== added 12 Lug 18:27 =========================

I've tried boot-repair using a ubuntu-secure-remix - I updated boot-repair before using it.

I've sent the error output posted at http://paste.ubuntu.com/1088164/ to boot.repair@gmail com

Boot-repair is suggesting other actions and I'll try

============= added 12 Lug 19:23 ==========================

Second try: non luck log at http://paste.ubuntu.com/1088300/

============= added 13 Lug 18:05 ==========================

At power-on magically the ubuntu boot entry appeared

Boot-repair was the solution