On Thursday, July 23, 2015 01:32:33 PM Fajar A. Nugraha wrote:
> > How do you folks get a working network with current wily containers?
>
> IIRC networking on unprivileged systemd container was broken due to
> some changes in systemd. This is true even on current release (vivid).
Yep, something f
Greetings, Fajar A. Nugraha!
> On Thu, Jul 23, 2015 at 1:23 PM, Mark Constable wrote:
>> On Thursday, July 23, 2015 08:55:21 AM Andrey Repin wrote:
>>> > *buntu wily host and unprivileged lxd containers. This used to work but
>>> > as you can see I seem to need dbus... on a headless server!
>>>
>
On Thu, Jul 23, 2015 at 1:23 PM, Mark Constable wrote:
> On Thursday, July 23, 2015 08:55:21 AM Andrey Repin wrote:
>> > *buntu wily host and unprivileged lxd containers. This used to work but
>> > as you can see I seem to need dbus... on a headless server!
>>
>> Yes, you need dbus. It is a generi
On Thursday, July 23, 2015 08:55:21 AM Andrey Repin wrote:
> > *buntu wily host and unprivileged lxd containers. This used to work but
> > as you can see I seem to need dbus... on a headless server!
>
> Yes, you need dbus. It is a generic communication service, has nothing to
> do with not being a
Greetings, Mark Constable!
> *buntu wily host and unprivileged lxd containers. This used to work but as
> you can see I seem to need dbus... on a headless server!
Yes, you need dbus. It is a generic communication service, has nothing to do
with not being a headless server.
--
With best regards
*buntu wily host and unprivileged lxd containers. This used to work but as
you can see I seem to need dbus... on a headless server!
lxc exec w1 -- bash -c 'systemctl restart networking.service'
Failed to get D-Bus connection: No such file or directory
Using a wily image from today, how do I start
On Wed, Jul 22, 2015 at 6:51 PM, Jian-Ming Zheng wrote:
> However, other hosts on the same network subnet (for example,
> 172.21.10.3) cannot connect to the container p1 via 172.21.0.2 and
> vice versa. For example, when using "ssh user@172.21.10.3" on p1, it
> shows that "No route to host." Moreo
Hello,
During a security audit of LXC by Roman Fiedler, two security issues
with LXC have been found and now fixed.
CVE 2015-1331:
This issue is related to LXC's use of /run/lock and /tmp as places
to write the container lockfile. As those two paths are world writable,
an attacker cou
Hi, All,
I have modified my host machine's network and set container to use
Host Bridge, but the container has network connection to only the
host.
Firstly, edit my Ubuntu host's /etc/network/interfaces to use bridge
br0 as follows:
auto br0
iface br0 inet dhcp
bridge_ports eth0
Restart the
You were right, that was the problem. I think I'll get rid of autofs on
our servers..
Thank you very much!
On 21.07.2015 18:26, Michael H. Warfield wrote:
> On Tue, 2015-07-21 at 13:20 +0200, André Janowicz wrote:
>> Hello,
>>
>> does anybody know why my containers complain once per
>> "lxc.mount
10 matches
Mail list logo
