On Sun, Aug 14, 2016 at 05:57:49PM +0300, Andrey Repin wrote: > Greetings, All! > > I've just figured out a problem, but can't seems to find a solution. > I have a number of containers serving content to the network through samba > shares. > > The containers' configuration is rather simple and does work for most part > just right. > > # Common configuration > lxc.include = /usr/share/lxc/config/ubuntu.common.conf > > # Container specific configuration > lxc.rootfs = /home/.lxc/build-trusty/rootfs > lxc.rootfs.backend = dir > lxc.utsname = build-trusty > lxc.arch = i686 > > # Network configuration > lxc.network.type = macvlan > lxc.network.macvlan.mode = bridge > lxc.network.link = eth0 > > lxc.network.hwaddr = 00:16:3e:69:05:85 > lxc.network.name = eth0 > lxc.network.flags = up > > The Samba configured as AD client, and here's the two lines that are related > to the problem: > > interfaces = lo, eth0
What if you get rid of the comma? (going by https://www.samba.org/~tpot/articles/multiple-interfaces.html) > bind interfaces only = Yes > > Now, the smbd is starting all right, and properly serving on lo, but failing > to bind to the eth0 for some reason. > Setting "bind interfaces only = No" lets it work, but that's not the desirable > configuration. > > Samba 4.3.11 > LXC 2.0.3 > > > -- > With best regards, > Andrey Repin > Sunday, August 14, 2016 17:45:49 > > Sorry for my terrible english... > > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
