Add Debian wheezy/sid base box templates #65

Closed
wants to merge 16 commits into
from

Conversation

Projects
None yet
2 participants
@Val
Contributor

Val commented Apr 25, 2013

  • Add Debian wheezy/sid base box templates
  • Refactor boxes rake task
  • Create common directory for common installation scripts
  • Move Debian/Ubuntu common installation scripts (puppet & chef)
  • Add babushka configuration engine support
Add Debian wheezy/sid base box templates
Refactor boxes rake task

Create common directory for common installation scripts

Move Debian/Ubuntu common installation scripts
@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Apr 25, 2013

Owner

@Val This is awesome, thanks a lot! I'll probably merge this over the weekend.

Owner

fgrehm commented Apr 25, 2013

@Val This is awesome, thanks a lot! I'll probably merge this over the weekend.

@Val

This comment has been minimized.

Show comment
Hide comment
@Val

Val Apr 25, 2013

Contributor

It works on Debian wheezy with :

lxc-template comes from ubuntu package / lxc upstream, not debian's one : too crappy with a lot of junk code for progress linux...)

Hope it helps.

Contributor

Val commented Apr 25, 2013

It works on Debian wheezy with :

lxc-template comes from ubuntu package / lxc upstream, not debian's one : too crappy with a lot of junk code for progress linux...)

Hope it helps.

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Apr 28, 2013

Owner

@Val I'm running Ubuntu Raring down here and wasn't able to boot a sid container I've built, I've had some issues related to networking which I'm not sure what's the reason behind it yet. I'll try it again as soon as possible and I'll post back some more information about it but in the meantime, would you be able to share the .box file you ended up with so that I can try it out down here and see if it works? Thanks

Owner

fgrehm commented Apr 28, 2013

@Val I'm running Ubuntu Raring down here and wasn't able to boot a sid container I've built, I've had some issues related to networking which I'm not sure what's the reason behind it yet. I'll try it again as soon as possible and I'll post back some more information about it but in the meantime, would you be able to share the .box file you ended up with so that I can try it out down here and see if it works? Thanks

@Val

This comment has been minimized.

Show comment
Hide comment
@Val

Val Apr 29, 2013

Contributor

I am not able to share .box for now (not enough bandwidth here).

I'll do some rework to properly cleanup generated debian boxes (downloaded packages, etc.)

Can you provide some logs of your networking tests with the sid box ?

Beware of HTTP_PROXY environment variable when building debian boxes, if sets it will configure container to use it after build...

Contributor

Val commented Apr 29, 2013

I am not able to share .box for now (not enough bandwidth here).

I'll do some rework to properly cleanup generated debian boxes (downloaded packages, etc.)

Can you provide some logs of your networking tests with the sid box ?

Beware of HTTP_PROXY environment variable when building debian boxes, if sets it will configure container to use it after build...

@fgrehm fgrehm referenced this pull request Apr 29, 2013

Closed

CentOS 6 base box #61

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Apr 29, 2013

Owner

I'll try to build it again to get you the log, I've also got some other small changes on top of your code which I might push to a branch so that you can also have a look as well ;-)

Owner

fgrehm commented Apr 29, 2013

I'll try to build it again to get you the log, I've also got some other small changes on top of your code which I might push to a branch so that you can also have a look as well ;-)

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Apr 29, 2013

Owner

@Val I've tried with a clean wheezy box now with no puppet / chef / babushka and I'm not able to boot it, I've also tried starting it by hand with lxc-start but it didn't work as well. Here's the output:

$ sudo lxc-start -n development-1367244623
lxc-start: Permission denied - failed to mount 'none' on '/usr/lib/x86_64-linux-gnu/lxc//dev/shm'
lxc-start: failed to setup the mounts for 'development-1367244623'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'development-1367244623'

I don't have the time to dig into this right now but if you have some spare time, would you be able to try to firing up the ubuntu raring VBox dev machine and try to start the box you've built from there?

Owner

fgrehm commented Apr 29, 2013

@Val I've tried with a clean wheezy box now with no puppet / chef / babushka and I'm not able to boot it, I've also tried starting it by hand with lxc-start but it didn't work as well. Here's the output:

$ sudo lxc-start -n development-1367244623
lxc-start: Permission denied - failed to mount 'none' on '/usr/lib/x86_64-linux-gnu/lxc//dev/shm'
lxc-start: failed to setup the mounts for 'development-1367244623'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'development-1367244623'

I don't have the time to dig into this right now but if you have some spare time, would you be able to try to firing up the ubuntu raring VBox dev machine and try to start the box you've built from there?

@Val

This comment has been minimized.

Show comment
Hide comment
@Val

Val Apr 29, 2013

Contributor

Ok, I'll do that.

I saw some other bugs, i'll fix them too.

Contributor

Val commented Apr 29, 2013

Ok, I'll do that.

I saw some other bugs, i'll fix them too.

@Val

This comment has been minimized.

Show comment
Hide comment
@Val

Val Apr 30, 2013

Contributor

@fgrehm I've now a working development environment like yours using raring64 virtualbox :

  • installed vagrant deb from vagrantup.com
  • twicked a bit development/Vagrantfile because of undefined Vagrant::Environment::DEFAULT_HOME (not commited)

debian LXC networking was broken, it should be fixed now.

Contributor

Val commented Apr 30, 2013

@fgrehm I've now a working development environment like yours using raring64 virtualbox :

  • installed vagrant deb from vagrantup.com
  • twicked a bit development/Vagrantfile because of undefined Vagrant::Environment::DEFAULT_HOME (not commited)

debian LXC networking was broken, it should be fixed now.

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Apr 30, 2013

Owner

@Val awesome, I'm building a wheezy box to try out on my laptop, I'll keep you posted

Owner

fgrehm commented Apr 30, 2013

@Val awesome, I'm building a wheezy box to try out on my laptop, I'll keep you posted

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm Apr 30, 2013

Owner

@Val For some weird reason I'm getting that same error on my laptop but it works from the VBox raring machine :( Thanks a lot for your work here, I'll just try to find out what's going on before merging this

Owner

fgrehm commented Apr 30, 2013

@Val For some weird reason I'm getting that same error on my laptop but it works from the VBox raring machine :( Thanks a lot for your work here, I'll just try to find out what's going on before merging this

@fgrehm

View changes

boxes/debian/lxc-template
+none $rootfs/dev/pts devpts defaults 0 0
+none $rootfs/proc proc defaults 0 0
+none $rootfs/sys sysfs defaults 0 0
+none $rootfs/dev/shm tmpfs defaults 0 0

This comment has been minimized.

@fgrehm

fgrehm Apr 30, 2013

Owner

@Val looks like I'm able to boot the container without this line, will it work for you if we get rid of it?

@fgrehm

fgrehm Apr 30, 2013

Owner

@Val looks like I'm able to boot the container without this line, will it work for you if we get rid of it?

This comment has been minimized.

@Val

Val Apr 30, 2013

Contributor

Then go for it, /dev/shm is not mandatory.

@Val

Val Apr 30, 2013

Contributor

Then go for it, /dev/shm is not mandatory.

@Val

This comment has been minimized.

Show comment
Hide comment
@Val

Val May 2, 2013

Contributor

21786ba should fix #68, rebuilding wheezy64 base box to test it now...

Contributor

Val commented May 2, 2013

21786ba should fix #68, rebuilding wheezy64 base box to test it now...

@fgrehm fgrehm referenced this pull request May 2, 2013

Merged

Debian boxes #70

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm May 2, 2013

Owner

@Val sorry but I don't see how 21786ba fixes the issue. My idea with that is to make sure vagrant-lxc clean up /tmp under the container rootfs after it has been shutdown, it's not related to the build process.

BTW, I've made some changes on top of your code which I'm planning to do some proper testing later on tonight, I'm closing this issue in favor of #70. Thanks a lot for your work on this :-)

Owner

fgrehm commented May 2, 2013

@Val sorry but I don't see how 21786ba fixes the issue. My idea with that is to make sure vagrant-lxc clean up /tmp under the container rootfs after it has been shutdown, it's not related to the build process.

BTW, I've made some changes on top of your code which I'm planning to do some proper testing later on tonight, I'm closing this issue in favor of #70. Thanks a lot for your work on this :-)

@fgrehm fgrehm closed this May 2, 2013

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm May 2, 2013

Owner

@Val just in case you want to have a look at the diff: Val:add_debian_box...debian-boxes

Owner

fgrehm commented May 2, 2013

@Val just in case you want to have a look at the diff: Val:add_debian_box...debian-boxes

@Val

This comment has been minimized.

Show comment
Hide comment
@Val

Val May 3, 2013

Contributor

All's Ok for me.

Contributor

Val commented May 3, 2013

All's Ok for me.

@fgrehm

This comment has been minimized.

Show comment
Hide comment
@fgrehm

fgrehm May 3, 2013

Owner

Awesome, I'll try to test a bit more over the weekend and if everything goes fine we'll have the changes merged in :-)

Owner

fgrehm commented May 3, 2013

Awesome, I'll try to test a bit more over the weekend and if everything goes fine we'll have the changes merged in :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment