Vagrant-lxc container not starting
I'm trying to start a previously download vagrant-lxc box that holds an Ubuntu 12.04 x32. My development PC is running Ubuntu 13.10 x64 and lxc 1.0.0.alpha1 installed from the Ubuntu official repositories. When I run vagrant up --provider=lxc I'm always getting
There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-lxc-test_default-1393431786", "--name", "lxc-test_default-1393431786", "-f", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/lxc.conf", "--", "--tarball", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/keys/vagrant.pub"]
I might be making a dumb error here so my questions are:
1- Is there any problem running a box of x32 container inside a x64 host using LXC?
2- Is there any problem running a box with a different Ubuntu version (Kernel version) that the host machine does? In may case (Ubuntu 12.04 (kernel 2.6) vs Ubuntu 13.10 (kernel 3.11))
3- In the case that 1, 2 do not apply, then, how can I figure out what's the problem? prep-ending VAGRANT_LOG=DEBUG didn't make the trick, it just shows the above errors many times.
4- In the case that 1 or 2 do apply, then, how can I overcome the situation?, I need fast and well performance on test virtual machines, (so I think I need containers), but it is no feasible to me that the developers should have the same OS as the testing VMs
linux ubuntu virtual-machine lxc vagrant
edited Jan 27 at 0:02
Rui F Ribeiro
39.9k1479134
asked Feb 26 '14 at 17:29
Carlos CastellanosCarlos Castellanos
15317
add a comment |
I'm trying to start a previously download vagrant-lxc box that holds an Ubuntu 12.04 x32. My development PC is running Ubuntu 13.10 x64 and lxc 1.0.0.alpha1 installed from the Ubuntu official repositories. When I run vagrant up --provider=lxc I'm always getting
There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-lxc-test_default-1393431786", "--name", "lxc-test_default-1393431786", "-f", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/lxc.conf", "--", "--tarball", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/keys/vagrant.pub"]
I might be making a dumb error here so my questions are:
1- Is there any problem running a box of x32 container inside a x64 host using LXC?
2- Is there any problem running a box with a different Ubuntu version (Kernel version) that the host machine does? In may case (Ubuntu 12.04 (kernel 2.6) vs Ubuntu 13.10 (kernel 3.11))
3- In the case that 1, 2 do not apply, then, how can I figure out what's the problem? prep-ending VAGRANT_LOG=DEBUG didn't make the trick, it just shows the above errors many times.
4- In the case that 1 or 2 do apply, then, how can I overcome the situation?, I need fast and well performance on test virtual machines, (so I think I need containers), but it is no feasible to me that the developers should have the same OS as the testing VMs
linux ubuntu virtual-machine lxc vagrant
edited Jan 27 at 0:02
Rui F Ribeiro
39.9k1479134
asked Feb 26 '14 at 17:29
Carlos CastellanosCarlos Castellanos
15317
Have you figured out anything about this use case?
– blong
Apr 7 '14 at 12:15
1
Yes, but I forgot to comment about it, the executing user needs to be part of sudoers, as for 1 and 2, there are not such problems, a workaround could be to erase all the contents under ~/.vagrant.d and start over if the doing the first fails.
– Carlos Castellanos
Apr 7 '14 at 14:04
Ah, ok. That's very helpful, thank you :)
– blong
Apr 7 '14 at 14:18
add a comment |
I'm trying to start a previously download vagrant-lxc box that holds an Ubuntu 12.04 x32. My development PC is running Ubuntu 13.10 x64 and lxc 1.0.0.alpha1 installed from the Ubuntu official repositories. When I run vagrant up --provider=lxc I'm always getting
There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-lxc-test_default-1393431786", "--name", "lxc-test_default-1393431786", "-f", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/lxc.conf", "--", "--tarball", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/keys/vagrant.pub"]
I might be making a dumb error here so my questions are:
1- Is there any problem running a box of x32 container inside a x64 host using LXC?
2- Is there any problem running a box with a different Ubuntu version (Kernel version) that the host machine does? In may case (Ubuntu 12.04 (kernel 2.6) vs Ubuntu 13.10 (kernel 3.11))
3- In the case that 1, 2 do not apply, then, how can I figure out what's the problem? prep-ending VAGRANT_LOG=DEBUG didn't make the trick, it just shows the above errors many times.
4- In the case that 1 or 2 do apply, then, how can I overcome the situation?, I need fast and well performance on test virtual machines, (so I think I need containers), but it is no feasible to me that the developers should have the same OS as the testing VMs
linux ubuntu virtual-machine lxc vagrant
edited Jan 27 at 0:02
Rui F Ribeiro
39.9k1479134
asked Feb 26 '14 at 17:29
Carlos CastellanosCarlos Castellanos
15317
I'm trying to start a previously download vagrant-lxc box that holds an Ubuntu 12.04 x32. My development PC is running Ubuntu 13.10 x64 and lxc 1.0.0.alpha1 installed from the Ubuntu official repositories. When I run vagrant up --provider=lxc I'm always getting
There was an error executing ["sudo", "lxc-create", "--template", "vagrant-tmp-lxc-test_default-1393431786", "--name", "lxc-test_default-1393431786", "-f", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/lxc.conf", "--", "--tarball", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/rootfs.tar.gz", "--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/keys/vagrant.pub"]
I might be making a dumb error here so my questions are:
1- Is there any problem running a box of x32 container inside a x64 host using LXC?
2- Is there any problem running a box with a different Ubuntu version (Kernel version) that the host machine does? In may case (Ubuntu 12.04 (kernel 2.6) vs Ubuntu 13.10 (kernel 3.11))
3- In the case that 1, 2 do not apply, then, how can I figure out what's the problem? prep-ending VAGRANT_LOG=DEBUG didn't make the trick, it just shows the above errors many times.
4- In the case that 1 or 2 do apply, then, how can I overcome the situation?, I need fast and well performance on test virtual machines, (so I think I need containers), but it is no feasible to me that the developers should have the same OS as the testing VMs
linux ubuntu virtual-machine lxc vagrant
linux ubuntu virtual-machine lxc vagrant
edited Jan 27 at 0:02
Rui F Ribeiro
39.9k1479134
asked Feb 26 '14 at 17:29
Carlos CastellanosCarlos Castellanos
15317
edited Jan 27 at 0:02
Rui F Ribeiro
39.9k1479134
asked Feb 26 '14 at 17:29
Carlos CastellanosCarlos Castellanos
15317
edited Jan 27 at 0:02
Rui F Ribeiro
39.9k1479134
edited Jan 27 at 0:02
Rui F Ribeiro
39.9k1479134
edited Jan 27 at 0:02
Rui F Ribeiro
39.9k1479134
39.9k1479134
asked Feb 26 '14 at 17:29
Carlos CastellanosCarlos Castellanos
15317
asked Feb 26 '14 at 17:29
Carlos CastellanosCarlos Castellanos
15317
asked Feb 26 '14 at 17:29
Carlos CastellanosCarlos Castellanos
15317
15317
Have you figured out anything about this use case?
– blong
Apr 7 '14 at 12:15
1
Yes, but I forgot to comment about it, the executing user needs to be part of sudoers, as for 1 and 2, there are not such problems, a workaround could be to erase all the contents under ~/.vagrant.d and start over if the doing the first fails.
– Carlos Castellanos
Apr 7 '14 at 14:04
Ah, ok. That's very helpful, thank you :)
– blong
Apr 7 '14 at 14:18
add a comment |
Have you figured out anything about this use case?
– blong
Apr 7 '14 at 12:15
1
Yes, but I forgot to comment about it, the executing user needs to be part of sudoers, as for 1 and 2, there are not such problems, a workaround could be to erase all the contents under ~/.vagrant.d and start over if the doing the first fails.
– Carlos Castellanos
Apr 7 '14 at 14:04
Ah, ok. That's very helpful, thank you :)
– blong
Apr 7 '14 at 14:18
Have you figured out anything about this use case?
– blong
Apr 7 '14 at 12:15
Have you figured out anything about this use case?
– blong
Apr 7 '14 at 12:15
1
1
Yes, but I forgot to comment about it, the executing user needs to be part of sudoers, as for 1 and 2, there are not such problems, a workaround could be to erase all the contents under ~/.vagrant.d and start over if the doing the first fails.
– Carlos Castellanos
Apr 7 '14 at 14:04
Yes, but I forgot to comment about it, the executing user needs to be part of sudoers, as for 1 and 2, there are not such problems, a workaround could be to erase all the contents under ~/.vagrant.d and start over if the doing the first fails.
– Carlos Castellanos
Apr 7 '14 at 14:04
Ah, ok. That's very helpful, thank you :)
– blong
Apr 7 '14 at 14:18
Ah, ok. That's very helpful, thank you :)
– blong
Apr 7 '14 at 14:18
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f117088%2fvagrant-lxc-container-not-starting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f117088%2fvagrant-lxc-container-not-starting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you figured out anything about this use case?
– blong
Apr 7 '14 at 12:15
1
Yes, but I forgot to comment about it, the executing user needs to be part of sudoers, as for 1 and 2, there are not such problems, a workaround could be to erase all the contents under ~/.vagrant.d and start over if the doing the first fails.
– Carlos Castellanos
Apr 7 '14 at 14:04
Ah, ok. That's very helpful, thank you :)
– blong
Apr 7 '14 at 14:18