Closed condector closed 5 years ago
Warning: Permanently added 'vm02.maas.mtl' (ECDSA) to the list of known hosts.
root@vm02:~# snap install lxd ; lxd.migrate -yes ; snap install lxd-demo-server ; snap connect lxd-demo-server:lxd lxd:lxd
2018-12-14T21:11:06Z INFO Waiting for restart...
lxd 3.7 from 'canonical' installed
=> Connecting to source server
=> Connecting to destination server
=> Running sanity checks
The source server is empty, no migration needed.
The migration is now complete and your containers should be back online.
All done. You may need to close your current shell and open a new one to have the "lxc" command work.
To migrate your existing client configuration, move ~/.config/lxc to ~/snap/lxd/current/.config/lxc
lxd-demo-server 0+git.f3532e3 from Stéphane Graber (stgraber) installed
root@vm02:~# lxd init
Would you like to use LXD clustering? (yes/no) [default=no]:
Do you want to configure a new storage pool? (yes/no) [default=yes]:
Name of the new storage pool [default=default]:
Name of the storage backend to use (btrfs, ceph, dir, lvm, zfs) [default=zfs]:
Create a new ZFS pool? (yes/no) [default=yes]:
Would you like to use an existing block device? (yes/no) [default=no]:
Size in GB of the new loop device (1GB minimum) [default=15GB]:
Would you like to connect to a MAAS server? (yes/no) [default=no]:
Would you like to create a new local network bridge? (yes/no) [default=yes]:
What should the new bridge be called? [default=lxdbr0]:
What IPv4 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
What IPv6 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
Would you like LXD to be available over the network? (yes/no) [default=no]:
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]
Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]:
root@vm02:~# lxd-demo-server.configure
root@vm02:~#
root@vm02:~# journalctl -u snap.lxd-demo-server.daemon -n 30
-- Logs begin at Fri 2018-12-14 21:02:32 UTC, end at Fri 2018-12-14 21:14:26 UTC. --
Dec 14 21:11:56 vm02 systemd[1]: Started Service for snap application lxd-demo-server.daemon.
root@vm02:~# lxc list
To start your first container, try: lxc launch ubuntu:18.04
+-------------+---------+---------------------+-----------------------------------------------+------------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+-------------+---------+---------------------+-----------------------------------------------+------------+-----------+
| tryit-known | RUNNING | 10.203.248.4 (eth0) | fd42:f2ae:2d14:5b2b:216:3eff:fe90:b8a9 (eth0) | PERSISTENT | |
+-------------+---------+---------------------+-----------------------------------------------+------------+-----------+
root@vm02:~#
So seems to be all working out of the box here. Anything special with your setup which would differ from this?
Yes,
I installed using the steps on the readme. Worked. But I need to translate index.html, so I removed the snap lxd-demo-server and run the go
commands to install the dependencies and build lxd-demo-server.
When I do that, the compiled allow me to translate, but not create containers.
I delete the GitHub lxd-demo-server directory and try to install again from snap. And the presented error continue to appear. Maybe a Go library inconsistency because I run that command to install dependencies from the Internet?
A pointer exception on http.
panic serving 10.87.0.42:44978: runtime error: invalid memory address or nil pointer dereference
And the page works, but not start any container.
Any way to clean up hardly to try again? I´m searching how to remove the libraries installed by this command:
go get github.com/lxc/lxd-demo-server
I tried this command:
go clean -i -n github.com/lxc/lxd-demo-server
Not solved yet. If nothing works I will reinstall all server. Probably something goes wrong. My concern was about this nil pointer dereference.
It's unclear what gets you into this situation. I've just manually built lxd-demo-server here and it's working properly when built from Go.
What's the lxd-demo.yaml
that you're using? And are you running lxd-demo-server
from within the source directory where the config is located?
Hum, weird situation for sure. Here is my lxd-demo.yaml
:
I create an alias for Debian container:
` $ lxc image ls
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE | +--------+--------------+--------+---------------------------------------+--------+----------+-------------------------------+ | debian | 7b19f99f5fd8 | no | Debian stretch amd64 (20181213_11:35) | x86_64 | 110.29MB | Dec 14, 2018 at 12:19pm (UTC) | `
That reproduced the issue here, will look into it
Ubuntu: 18.04 LXD: 3.7
The log from lxd-demo-server: