Re: [vagrant] official Debian lxc boxes
Le 04/02/2016 17:14, Antonio Terceiro a écrit :
> On Thu, Feb 04, 2016 at 12:35:15PM -0200, Tiago Ilieve wrote:
>> Hi Antonio,
>>
>> On 4 February 2016 at 09:48, Antonio Terceiro <terceiro@debian.org> wrote:
>>> That said I noted that we did not have a recent build after v8.1,
>>> so I am uploading one just now.
>>
>> The problem with outdated images maintained by us is becoming more
>> common every day. Looks like Martin Zobel-Helas and Bastian Blank did
>> an awesome job regarding this with the Jenkins infrastructure they
>> built for Azure images at Credativ.
>>
>> Don't you think that is the time for us to do something like that?
>> Maybe not that sophisticated for start, but something that we could
>> use for building those images more frequently. Bonus points if we can
>> share/integrate this with the Debian CD team.
>
> Sure.
>
> I am only maintaing the vagrant lxc images because I use them, and as
> the maintainer of vagrant and vagrant-lxc I feel that's needed because
> with them one can use vagrant without anything outside of main. The code
> I use is in the debian-vm-templates repository (directory
> custom-lxc-vagrant), I just build the images (e.g. `sudo make
> jessie.box`) and upload them to the debian atlas account whenever I
> remember, or when I am reminded like today.
>
> I will be more than happy to stop having to do that once such an
> automated process is in place! AFAICT Emmanuel is already talking to the
> CD team about that.
>
Yes Steve from the cd team agreed about the idea but nothing has been
done yet (everyone is busy, that's life) I am also considering looking
for a sponsor for a build server inside this list:
https://wiki.debian.org/ServicesHosting#Outside_the_Debian_infrastructure
BTW I had a try yesterday with the Vagrant LXC template and I noticed my
login prompt inside started to talk to me in a different latin language.
I suspect this comes from /usr/share/lxc/templates/lxc-debian
which has
chroot $rootfs update-locale LANG=$LANG
Emmanuel
Reply to: