<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 10/21/2017 06:12 AM, Fajar A.
Nugraha wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG1y0sc=b-pNc7G5nu6H=Vxv0T+EVYn2digBPCB=uRYrQzQBkA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><br>
<div><br>
</div>
<div>Note that it's MUCH easier to use lxd on ubuntu 16.04,
with xenial-backports to get the 'best' combination of
'new features' and 'tested'. It has lxd 2.18, with support
for storage pools. If you're using this version, the most
relevant documentation would be from git master branch: <a
href="https://github.com/lxc/lxd/tree/master/doc"
moz-do-not-send="true">https://github.com/lxc/lxd/tree/master/doc</a></div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
Thank you very much<br>
<blockquote type="cite"
cite="mid:CAG1y0sc=b-pNc7G5nu6H=Vxv0T+EVYn2digBPCB=uRYrQzQBkA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>If you're using it for production and want long term
support, use the default xenial repository instead (not
backports), which has lxd 2.0.x. It's supported for longer
time, but doesn't have new features (like storage pools).
The relevant docs for this version is either <a
href="https://github.com/lxc/lxd/tree/stable-2.0/doc"
moz-do-not-send="true">https://github.com/lxc/lxd/tree/stable-2.0/doc</a>
or <a
href="https://help.ubuntu.com/lts/serverguide/lxd.html"
moz-do-not-send="true">https://help.ubuntu.com/lts/serverguide/lxd.html</a></div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
2- How do I erase my first trial : I try to reinit but i
says me that :<br>
<br>
The requested storage pool "default" already exists.
Please choose another name.<br>
<br>
How do I erase the the storage pool "default" ?<br>
</blockquote>
<div><br>
</div>
<div>Might be hard if you're using file-backed zfs-pool. On
ubuntu it's probably something like this:</div>
<div>- systemctl disable lxd</div>
<div>- reboot</div>
<div>- rename /var/lib/lxd to something else, then create an
empty /var/lib/lxd</div>
<div>- systemctl enable lxd</div>
<div>- systemctl start lxd</div>
<div>- lxd init</div>
<div><br>
</div>
<div>I'm not sure how the path and startup script would
translate to debian + lxd from snapd (which is in the link
you mentioned)</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
I have not successed. But as it is a new server, I reinstall all !<br>
<blockquote type="cite"
cite="mid:CAG1y0sc=b-pNc7G5nu6H=Vxv0T+EVYn2digBPCB=uRYrQzQBkA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<br>
3- My true problem is that I do not want the NAT for my
new lxc containers but that they use the normal addresses
on my local network. How do I do that ?<br>
<br>
</blockquote>
<div><br>
</div>
<div>The usual way:</div>
<div>- create your own bridge, e.g. br0 in <a
href="https://help.ubuntu.com/community/NetworkConnectionBridge"
moz-do-not-send="true">https://help.ubuntu.com/community/NetworkConnectionBridge</a>
(that example bridges eth0 and eth1 on the same bridge.
use the relevant public interface for your setup)</div>
<div>- configure your container (or profile) to use it
(replacing the default lxdbr0). </div>
<div>- no need to delete existing lxdbr0, just leave it as
is.<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>The 'new' way: looking at <a
href="https://github.com/lxc/lxd/blob/master/doc/networks.md"
moz-do-not-send="true">https://github.com/lxc/lxd/blob/master/doc/networks.md</a>
, it should be possible to create the bridge using 'lxc
network create ...'</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
And how do I assign them a MAC address so they are
accessible from the internet.<br>
<br>
</blockquote>
<div><br>
</div>
<div>This depends on your setup.</div>
<div><br>
</div>
<div>For example, if you rent dedicated server from
serverloft (or other providers with similar networking
setup), they do NOT allow bridging of VMs to the public
network. You need to setup routing instead (long story).</div>
<div><br>
</div>
<div>But if you're on a LAN, then 'making the containers be
on the same LAN is the host' is as simple as 'configure
the container to use br0' (or whatever bridge you create
above). If the LAN has a DHCP server, then the container
will automatically get a 'public' IP addres. If not, then
configure it statically (just like how you configure a
normal linux host)</div>
<div><br>
</div>
<div>--<br>
</div>
</div>
</div>
</div>
</blockquote>
Thanl you.<br>
<blockquote type="cite"
cite="mid:CAG1y0sc=b-pNc7G5nu6H=Vxv0T+EVYn2digBPCB=uRYrQzQBkA@mail.gmail.com"><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
lxc-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a>
<a class="moz-txt-link-freetext" href="http://lists.linuxcontainers.org/listinfo/lxc-users">http://lists.linuxcontainers.org/listinfo/lxc-users</a></pre>
</blockquote>
<br>
</body>
</html>