>From man lxc.container.conf When the system boots with the LXC service enabled, it will first attempt to boot any containers with lxc.start.auto == 1 that is a member of the "onboot" group. The startup will be in order of lxc.start.order. If an lxc.start.delay has been specified, that delay will be honored before attempting to start the next container to give the current container time to begin initialization and reduce overloading the host system. After starting the members of the "onboot" group, the LXC system will proceed to boot containers with lxc.start.auto == 1 which are not members of any group (the NULL group) and proceed as with the onboot group.
Which is very explicit that what you are experiencing is not the default behavior. I 've never had a problem with that. Is it possible that the order is respected but the first containers are just slower to start up? 2015-02-28 20:52 GMT-05:00 Bostjan Skufca <[email protected]>: > I understood from man pages that lxc.start.order setting should cause > containers to start in ascending order (lower the value, earlier the > startup). It turns out that with 1.0.7 this acts more like priority - the > higher the value, the sooner container starts. > > Is anyone else experiencing this with lxc-autostart? Is this intended > behaviour? > > b. > > > _______________________________________________ > 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
