Yes, the way the ssh was assembled was a bit rough--running sed over the dhcp leases to find the ip address of the container name. In the solution I proposed on this bug, we were going to initially do the same within the command string. At least the hack would not be in lxc itself. Later we might be able to make it a bit more pleasant by using avahi in the container and sshing to [container name].local.
My best understanding of lxc-execute is that it won't be sufficient. We need a number of system services to run Launchpad tests, especially Apache and Postgres. However, I'm happy to be educated and shown to be wrong--perhaps we could write a custom script that would start what we needed and then do the actual job we want. The fact we have to use sudo with this solution (AIUI) is a bit of a problem too: we want automated processes to run this, and we really don't want to run them with root privileges, nor with a root password. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/914169 Title: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/914169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
