[lxc-users] Accessing lxd containers?

[Craig Tataryn]

Hmm, iptables magic tends to work for me. Here's what I did to forward SSL
traffic to one of my containers.

sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j DNAT --to
10.0.3.115:443

Craig

On Thu, Jun 30, 2016 at 10:33 AM, Kim C. Callis <kim.callis at gmail.com>
wrote:

> When I did lxc containers, I tended to just put a container directly on
> the LAN and call it a day. With my lxd container i would like to access via
> lxdbr0 and just access ports as needed.
>
> I thought that my forwarding and iptables magic, I would be good to go...
> I was wrong! So what is the magic of accessing a port and how about via
> static routing in case I want full access?
>
> Any pointers would be greatly appreciated!
>
> K. Callis
> On Jun 30, 2016 8:34 AM, "Serge E. Hallyn" <serge at hallyn.com> wrote:
>
>> On Thu, Jun 30, 2016 at 01:06:17PM +0200, Michele Giacomoli wrote:
>> > Hi,
>> >
>> > I'd like to setup auditd inside an unprivileged container running
>> > Ubuntu 14.04. Tried installing auditd package but nothing being
>> > logged. Trying /etc/init.d/auditd start I get:
>> >
>> >  * Starting audit daemon auditd
>> >    ...fail!
>> >
>> > auditd package is installed also in lxc host (Ubuntu 14.04 too) and
>> > is working.
>> >
>> > So my question is: can audit work inside an lxc guest? If so, how?
>>
>> No.
>> _______________________________________________
>> lxc-users mailing list
>> lxc-users at lists.linuxcontainers.org
>> http://lists.linuxcontainers.org/listinfo/lxc-users
>
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>



-- 
Craig Tataryn
blog: http://tataryn.net
podcast: http://www.basementcoders.com/
irc: ThaDon on freenode #basementcoders
twitter: @craiger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20160630/3eefbe49/attachment.html>