On Mon, Jun 27, 2016 at 10:05 PM, ronkaluta wrote:
>
> As a follow up to my last post
> #-
> # The network interfaces sometimes get mixed up.
> #-
> lxc config edit ${CONTAINER}
> # example
> #
> name: x2go1248
> profiles:
> - bridge
As a follow up to my last post
#-
# The network interfaces sometimes get mixed up.
#-
lxc config edit ${CONTAINER}
# example
#
name: x2go1248
profiles:
- bridge
config:
volatile.base_image:
89715de6a3e329ecb10af529cb81c33c157a5124
On Mon, Jun 27, 2016 at 5:15 PM, wrote:
> However, I cannot ping an outside IP:
> root@taskd:~# ping
> 8.8.8.8
>
> PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
>
> On the host I see:
> 11:30:14.343238 IP 10.0.8.54 > google-public-dns-a.google.com: ICMP echo
> request, id 12902, seq 1, length 64
>
Hi David,
In the situation of the issue, you have to sniff where the packets go or get
lost and if it's the outgoing or incoming direction. As the packet source and
destination is notated at Layer3 (IP), but the way is chosen by the layer2
(MAC), you had to look at routing tables, arp informati
Please forgive the long-winded explanation but I think better to be
explicit rather than leave people guessing.
I have been using LXD containers ever since its birth and prefer it to
LXC containers (my personal preference.)
The ease of use and migration between hosts is a definite plus.
I have s
Brian
Thank you for this link!
I have read through it and it indeed seems related, or maybe the same thing as
some of those.
My problem clearly isn't related to DNS, since I cannot ping out by IP as well.
And since I see this exact same behavior on two hosts (one physical, one
virtual) on two di
Ok, I find the main error; it was because I tried to modify the first hexa
number:
http://askubuntu.com/questions/423530/cant-change-my-mac-address-cant-assign-requested-address
However, the "volatile" way still does not work. Anyway, I prefer the first
one.
My LXD version is 2.0.2.
Cheers
201
david
rather than using ping what does traceroute show you?
Your problem sounds an awful lot like what many Docker users started
reporting in this long thread
https://github.com/docker/docker/issues/13381
If you take the time to read through all of it you will notice several
people came up with
Ok, this happens again and again!
Like this LXD is not usable in production. I cannot restart LXD every few days.
I'll answer Fajar's questions from below here:
By "inbound" I mean connections from the host/internet to he container. Those
work and keep working. I have port forwarding enabled.
By
> Von: lxc-users [mailto:lxc-users-boun...@lists.linuxcontainers.org] Im
> Auftrag
>
> Quoting Fiedler Roman (roman.fied...@ait.ac.at):
> > Hello List,
> >
> > With LXC1 on Trusty following sequence was used to fill an unprivileged
> > container as root, where only configuration exists but no cont
I understand that live migration is not stable.
I have seen a note to migrate from one user to another user inside a host :
http://unix.stackexchange.com/questions/156477/migrate-an-unprivileged-lxc-container-between-users
But is it possible to migrate stopped containers (host under jessie)
from
11 matches
Mail list logo
