On Tue, Jun 2, 2015 at 8:19 AM Anders Ingemann wrote:
> > Chef is already doing this where the bento boxes are provisionerless
> and the vagrant-omnibus plugin installs the version of Chef to your liking.
> This! Definitely the way to go. Is there anything required of the box for
>
> Chef is already doing this where the bento boxes are provisionerless and
the vagrant-omnibus plugin installs the version of Chef to your liking.
This! Definitely the way to go. Is there anything required of the box for
that solution to work, or is all you need apt-get?
On Tue, Jun 2, 2015 at 12:
I think we are in need of some kind of policy here.
The idea of those images is that you can download them and they are
ready-to-use (which means pre-installing software).
This is in direct conflict with Debian branded images, because we want them
to be as close to the standard distribution as poss
Interesting. How/when was the image generated? The vagrant plugin for
bootstrap-vz uses (ALL):
https://github.com/andsens/bootstrap-vz/blob/c94e172ea19f9e44314272deb3137d74253c9411/bootstrapvz/plugins/vagrant/tasks.py#L70
On Sun, May 31, 2015 at 9:06 AM Martey Dodoo <
bugs.debian@marteydodoo.c
>
> but the reality is that getty processes exist in the official Jessie HVM
> AMI
Ooh! And I know why :-)
The HVM AMIs are generated from James Brombergers fork, which most likely
does not have those adjustments.
OK, the issue here is then that James and I need to get together and figure
out this
On 18 May 2015 at 15:43, Ognyan Kulev wrote:
> "I'm a little confused, we should already be doing that for AWS images:
> https://github.com/andsens/bootstrap-vz/blob/f3be3e4543a37ef1af7b2b5193a8bb7b590d1b79/bootstrapvz/common/tasks/boot.py#L31
> "
>
> systemd does not use the /etc/inittab file.
>
On 18 May 2015 at 11:08, Marcin Kulisz wrote:
> I suppose it make sens on AWS to ditch getty process only issue I see with
> this
> it's taking us a bit further (like diverge more) from the 'default Debian
> image' and this may cause some issues.
> --
>
> |_|0|_|
On 29 July 2014 15:30, Olivier Berger
wrote:
> Hi.
>
> Charles Plessy writes:
>
> > One reason why bootstrap-vz exists is that broader frameworks such as
> > Debian-Installer have more constraints and are harder to learn and
> maintain.
> > In particular, Debian-Installer does not run as a simpl
On 1 May 2014 00:59, Chris Fordham wrote:
> Personally, I'd prefer that we use packer instead of bootstrap-vz (
> https://github.com/andsens/bootstrap-vz) to build official Debian images
> of which should be published on http://cdimage.debian.org or the more
> appropriate file server for users to
tion Architect | Amazon Web Services
>
> *E: *jame...@amazon.com* P:* +61 422 166 708 *T:*@JamesBromberger
>
>
>
> *From:* Jimmy Kaplowitz [mailto:jkaplow...@google.com]
> *Sent:* Tuesday, 8 April 2014 5:22 PM
> *To:* Anders Ingemann; 743...@bugs.debian.org
>
On 8 April 2014 09:28, Charles Plessy wrote:
> Le Tue, Apr 08, 2014 at 09:02:12AM +0200, Anders Ingemann a écrit :
> >
> > It's hanging because I never got an answer to my question: What's the
> > difference between:
> >
> > http://security.debia
On 8 April 2014 02:48, Jonathan Landis wrote:
>
> Package: cloud.debian.org
>
> The heartbleed bug has created a situation in which servers must be
upgraded immediately. At the moment the default mirrors listed in the
Debian Wheezy AMI image don't have the patches yet, but
security.debian.orgdoes.
On 29 January 2014 02:38, Jimmy Kaplowitz wrote:
> Set the hostname to localhost in build-debian-cloud. The standard
> set_hostname logic in /sbin/dhclient-script will override this just fine,
> but it should fix the log clutter.
>
> - Jimmy
>
Good idea. I already do it for the vagrant plugin:
h
A helpful finn fixed it:
https://github.com/andsens/ec2debian-build-ami/commit/6fd56203c7f0b2df18ce4fc247a2c0d9a8ee5b6b
Anders
On 6 January 2013 22:55, Chris Fordham wrote:
> This is a good example of why template-based configuration is better used
> rather than regex/stream based editing.
well. d'uh! :-P
I did not know about sudoers.d when I wrote it, otherwise I can assure
you that we wouldn't be talking about this to
On 6 January 2013 18:48, Thomas Goirand wrote:
> On 01/07/2013 12:00 AM, Ian Campbell wrote:
>> On Sun, 2013-01-06 at 17:53 +0900, Charles Plessy wrote:
>>> The only other interruption is the following debconf question from
>>> libc6:
>>>
>>> Restart services during package upgrades withou
You are right, sudoers.d should be used, this would also fix the
problem with wheezy, where my sed command does not work, because the
layout of the file has changed.
Anders
On 6 January 2013 10:16, Charles Plessy wrote:
> forwarded 697490 https://github.com/andsens/ec2debian-build-ami/issues/43
On 27 December 2012 11:28, Charles Plessy wrote:
> Le Tue, Dec 18, 2012 at 03:14:02PM +0100, Stefano Zacchiroli a écrit :
>> On Mon, Dec 17, 2012 at 02:11:52PM -0800, Clint Byrum wrote:
>> > How is it a slippery slope if it is driven by data?
>> >
>> > Seriously, figure out a way to ask users what
On 27 December 2012 12:26, Charles Plessy wrote:
>
> Package: cloud.debian.org
> Severity: normal
>
> Hi all,
>
> there is one "failed" error message in the boot messages of our official
> instances ran on the AWS.
>
> startpar: service(s) returned failure: hostname.sh ... failed!
>
> I am not s
On 27 December 2012 12:08, Charles Plessy wrote:
> Package: cloud.debian.org
> Severity: normal
>
> Dear James and Anders,
>
> Our official images are configured with the en_US.UTF-8 locale generated, but
> on the other hand there is no default. As a consequence, when I log in by
> SSH,
> the lo
Most certainly, I have a standard-packages plugin which is supposed to
install the packages one would expect to see in a base install.
This plugin also installs less. I think I should remove vim and emacs from
it though.
You can see the list here:
https://github.com/andsens/ec2debian-build-ami/blob
21 matches
Mail list logo
