Hello, I am trying to create a virtualbox image from my stretch system.
But I hve two problems 
I took your example from the DiskImage property, but in the end, I got this
/srv/diskimages/soleil.img.chroot no services started ... ok
/srv/diskimages/soleil.img.chroot has Operating System (Debian Linux Unstable) X86_32 ... ok
/srv/diskimages/soleil.img.chroot apt installed linux-image-i686 ... ok
/srv/diskimages/soleil.img.chroot grub package installed ... ok
/srv/diskimages/soleil.img.chroot root has insecure password ... done
/srv/diskimages/soleil.img.chroot account for soleil ... ok
/srv/diskimages/soleil.img.chroot soleil has insecure password ... done
/srv/diskimages/soleil.img.chroot user soleil in group audio ... ok
/srv/diskimages/soleil.img.chroot user soleil in group cdrom ... ok
/srv/diskimages/soleil.img.chroot user soleil in group dip ... ok
/srv/diskimages/soleil.img.chroot user soleil in group floppy ... ok
/srv/diskimages/soleil.img.chroot user soleil in group video ... ok
/srv/diskimages/soleil.img.chroot user soleil in group plugdev ... ok
/srv/diskimages/soleil.img.chroot user soleil in group netdev ... ok
/srv/diskimages/soleil.img.chroot user soleil is in standard desktop groups ... ok
/srv/diskimages/soleil.img.chroot cache cleaned ... ok
0 0% 0.00kB/s 0:00:00 (xfr#0, to-chk=0/3)
930 0% 1.77kB/s 0:00:00 (xfr#3, to-chk=0/11069)
chroot: impossible d'exécuter la commande « update-initramfs »: No such file or directory
loop deleted : /dev/loop0
I will try to add the pacakge which contain update-initramfs and report back
the second problem is thaht virtualbox is no more part of stretch. So it is not possible to create a virtualbox image.
Cheers
Frederic
OK, I tryed to install the wrong kernel so the initramfs was not installed.
So now the only real problem is the virtualbox one
Cheers
Frederic
It seems that we do not need virtualbox in order to generate a vmdk image
I installed qemu-utils and then
what about using this solution instead of the virtualbox one ?
Cheers
seems to work
The
vmdkBuiltForproperty is provided to make a disk image usable with virtualbox. If your distribution chooses not to include virtualbox and so you don't have virtualbox installed, what good would such an image be to you?To use
vmdkBuiltForyou must already have a disk image file, which qemu etc can already use."qemu-img convert" writes a whole disk image file. This is a much more expensive operation than what
vmdkBuiltForcurrently does, which creates a tiny text file that makes virtualbox use the existing disk image.this is good for me because I prepare a virtualbox image not for me but for our windows / MacOSX users.
This is why I need to build these images.
thanks for your help
The vmdk text file is so small that I did think about just having propellor generate it by itself. I don't know how stable/documented it is however.
I suppose that if you're distributing a vmdk image to others, you would not want to use the text file format, since that hard-codes the path to the .img file. So, perhaps there should be separate properties for vmdk text files that point at disk images and self-contained vmdk images.
It is true that my uszer prefer the embeded virtual image :).
Maybe we could have a DiskImage export property which could take an output format type I do not know how many format are out there for these kind of virtual machines. Maybe this could be also a way to prepare images for the cloud. (I do not use this mayself but why not). What is the difference between Diskimage and containers ?
Cheers
Frederic
The
DiskImagedata type could be expanded to support different output formats.Or, a type class could be used, so eg:
The type class would just need a function to convert from the raw disk image to the desired file format. Then anyone could add whatever disk image formats they want (which can probably shade into containers in some cases).
If I understand correctly, the new typeclass need to provide a method which return the (RawDiskImage filename). In the process we have at least 2 cache level One for the chroot, and one for the RawImage.
I was wondering if these cache (side effect) could not be regrouped under /var/cache/propellor instead of putting this randomly everywhere on the disk.
This way It should be possible to "reset" propellor by removing the cache in order to force a cache rebuild.
I think about this because I am not aware as a user of all these "side effects".
propellor --purge-cache
cheers and thanks again
Yes, there are two levels of caches. This does make updating the images a whole lot faster!
Some systems don't have a very large /var partition and so I think it's better to let the user pick where they go. The documentation could certainly (always) be improved.
Note that reverting any of the properties in DiskImage will clean up all the cache files as well as the final disk image.