[lxc-users] Are host's network bridge device name other than "lxcbr0" is supported with user-space lxc? (Ubuntu 14.04 64bit host)

[Adam Ryczkowski]

I am stuck with this problem for a long time now, so if you don't have 
time to read the whole mail, just please answer "yes, multiple bridge 
interfaces are supported", or "no, whole unprivileged lxc network 
infrastructure is limited to just one system-wide bridge interface", so 
at I can plan accordingly and move forward...

* * *

When I replace "lxcbr0" with "lxcbr1" in the /etc/lxc/lxc-usernet, 
create the lxcbr1 the same way as lxcbr0 is created and reflect the 
change in the container's configuration (replacing "lxc.network.link = 
lxcbr0" with "lxc.network.link = lxcbr1") I get an error:


        lxc-start 1422538264.345 INFO     lxc_start_ui - 
lxc_start.c:main:265 - using rcfile 
/home/alxc/.local/share/lxc/adasik/config
        lxc-start 1422538264.346 INFO     lxc_confile - 
confile.c:config_idmap:1325 - read uid map: type u nsid 0 hostid 296608 
range 65536
        lxc-start 1422538264.346 INFO     lxc_confile - 
confile.c:config_idmap:1325 - read uid map: type g nsid 0 hostid 296608 
range 65536
        lxc-start 1422538264.346 WARN     lxc_log - 
log.c:lxc_log_init:316 - lxc_log_init called with log already 
initialized       lxc-start 1422538264.347 WARN     lxc_cgmanager - 
cgmanager.c:cgm_get:954 - do_cgm_get exited with error
        lxc-start 1422538264.347 INFO     lxc_lsm - 
lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
        lxc-start 1422538264.348 DEBUG    lxc_conf - 
conf.c:lxc_create_tty:3665 - allocated pty '/dev/pts/15' (5/6)
        lxc-start 1422538264.348 DEBUG    lxc_conf - 
conf.c:lxc_create_tty:3665 - allocated pty '/dev/pts/16' (7/8)
        lxc-start 1422538264.348 DEBUG    lxc_conf - 
conf.c:lxc_create_tty:3665 - allocated pty '/dev/pts/17' (9/10)
        lxc-start 1422538264.348 DEBUG    lxc_conf - 
conf.c:lxc_create_tty:3665 - allocated pty '/dev/pts/18' (11/12)
        lxc-start 1422538264.348 INFO     lxc_conf - 
conf.c:lxc_create_tty:3676 - tty's configured
        lxc-start 1422538264.348 DEBUG    lxc_start - 
start.c:setup_signal_fd:247 - sigchild handler set
        lxc-start 1422538264.348 DEBUG    lxc_console - 
console.c:lxc_console_peer_default:500 - opening /dev/tty for console peer
        lxc-start 1422538264.348 DEBUG    lxc_console - 
console.c:lxc_console_peer_default:506 - using '/dev/tty' as console
        lxc-start 1422538264.348 DEBUG    lxc_console - 
console.c:lxc_console_sigwinch_init:179 - 23869 got SIGWINCH fd 17
        lxc-start 1422538264.348 DEBUG    lxc_console - 
console.c:lxc_console_winsz:88 - set winsz dstfd:14 cols:213 rows:58
        lxc-start 1422538264.394 INFO     lxc_start - 
start.c:lxc_init:443 - 'adasik' is initialized
        lxc-start 1422538264.395 DEBUG    lxc_start - 
start.c:__lxc_start:1058 - Not dropping cap_sys_boot or watching utmp
        lxc-start 1422538264.395 INFO     lxc_start - 
start.c:lxc_spawn:802 - Cloning a new user namespace
        lxc-start 1422538264.395 INFO     lxc_cgroup - 
cgroup.c:cgroup_init:62 - cgroup driver cgmanager initing for adasik
        lxc-start 1422538264.441 ERROR    lxc_start - 
start.c:lxc_spawn:927 - failed to create the configured network
        lxc-start 1422538264.445 ERROR    lxc_start - 
start.c:__lxc_start:1080 - failed to spawn 'adasik'
        lxc-start 1422538264.451 ERROR    lxc_start_ui - 
lxc_start.c:main:342 - The container failed to start.
        lxc-start 1422538264.454 ERROR    lxc_start_ui - 
lxc_start.c:main:346 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

The whole configuration and other details are in my previous post, 
https://lists.linuxcontainers.org/pipermail/lxc-users/2015-January/008366.html 
.

Thank you,

Adam Ryczkowski
+48505919892 <callto:+48505919892>
Skype:sisteczko <skype:sisteczko>