With lxd 2.14:
# mkdir /tmp/testdir
# touch /tmp/testdir/file1 /tmp/testdir/file2
# lxc file push -r /tmp/testdir/ testvm1/tmp # < note the trailing
slash after /tmp/testdir/
# echo $?
0
# lxc exec testvm1 ls /tmp
file1 file2
With lxd 2.15:
# mkdir /tmp/testdir
# touch
On Thu, Jun 29, 2017 at 03:24:46AM +, Tomasz Chmielewski wrote:
> With lxd 2.14:
>
> # mkdir /tmp/testdir
> # touch /tmp/testdir/file1 /tmp/testdir/file2
> # lxc file push -r /tmp/testdir/ testvm1/tmp # < note the trailing
> slash after /tmp/testdir/
> # echo $?
> 0
> # lxc exec
On Wed, Jun 28, 2017 at 11:12 PM, Adil Baig wrote:
> I actually don't have a separate dnsmasq instance running on the host.
>
... and that, is the root cause of your problem.
But just `dig +short devop-tools.lxd` doesn't. Which means the queries are
> not being forwarded
How do i restart dnsmasq without restarting lxd? That would pause all my
containers.
On Wed, Jun 28, 2017 at 3:47 PM, Fajar A. Nugraha wrote:
> On Wed, Jun 28, 2017 at 4:36 PM, Adil Baig wrote:
>
>> In the new LXD (2.5+) is there automatic DNS resolution
In the new LXD (2.5+) is there automatic DNS resolution for containers on
the host?
I'd like to configure a virtual host on Apache (on the host mahcine) to
proxy requests to a container using its DNS rather than its IP. How can i
do this?
___
lxc-users
On Wed, Jun 28, 2017 at 4:36 PM, Adil Baig wrote:
> In the new LXD (2.5+) is there automatic DNS resolution for containers on
> the host?
>
>
It can. But you need to make it so.
> I'd like to configure a virtual host on Apache (on the host mahcine) to
> proxy requests to
This hasn't worked for me.
lxc network show lxdbr0
description: ""
config:
dns.domain: lxd
dns.mode: managed
ipv4.address: 10.0.1.1/24
ipv4.dhcp.ranges: 10.0.1.2-10.0.1.254
ipv4.nat: "true"
ipv6.address: none
raw.dnsmasq: conf-file=/home/ubuntu/stockopedia-lxd-dnsmasq.conf
name:
On Wed, Jun 28, 2017 at 6:12 PM, Adil Baig wrote:
> How do i restart dnsmasq without restarting lxd? That would pause all my
> containers.
>
>
The hosts's dsnsmasq. Not the one managed by lxd. systemctl restart dnsmasq.
And in any case, test on your dev system first. On
On Wed, Jun 28, 2017 at 6:34 PM, Adil Baig wrote:
> This hasn't worked for me.
>
> lxc network show lxdbr0
> description: ""
> config:
> dns.domain: lxd
> dns.mode: managed
> ipv4.address: 10.0.1.1/24
> ipv4.dhcp.ranges: 10.0.1.2-10.0.1.254
> ipv4.nat: "true"
>
I actually don't have a separate dnsmasq instance running on the host. It's
just the one that lxd manages. (DNS from inside the containers do work, but
that's not my concern)
I realised forwarding queries to the lxd dnsmasq does work, ex:
dig @10.0.1.1 +short devop-tools.lxd
10.0.1.66
But just
10 matches
Mail list logo