Differences between revisions 3 and 4
Revision 3 as of 2013-05-11 06:30:39
Size: 3014
Comment: Documenting third-party packages and scripts.
Revision 4 as of 2013-05-11 06:50:06
Size: 3163
Comment: Identifiers of cloud images.
Deletions are marked like this. Additions are marked like this.
Line 56: Line 56:

== Identifiers ==

 * AWS: 379101102735/debian-wheezy-amd64-YYYYMMDD
 * Azure: ?
 * GCE: debian-7-wheezy-vYYYYMMDD (project ID: debian-cloud)

List of differences between standard and cloud systems

The goal of this page is to list the differences, and organise which and how to resolve them. Here, standard refers to Debian systems installed with DebianInstaller with the default settings, following the instructions in http://www.debian.org/releases/stable/installmanual.

Eventually, we should converge on a consensus that the remaining differences, if any, do not prevent us to claim that the cloud images are genuine Debian systems (706052).

Availability of installer source code

  • Standard systems are prepared with DebianInstaller, which is packaged in the Debian archive. TODO: check if the source code of all scripts used to prepare the binary images of DebianInstaller (install CDs, etc.) is also packaged.

  • AWS and GCE images are prepared with build-debian-cloud, to be packaged (693198). TODO: How about Azure images ?

Distribution Binary images

  • Debian does not distribute binary images of standard systems, but distributes installation media with a binary image of DebianInstaller.

  • AWS, Azure and GCE images are available on the respective public clouds.
  • Distribution of a generic cloud image in the debian archive is under discussion.
  • TODO: How about the Debian live images ?

Contents (Stable systems)


  • All: only the main area is enabled by default (not contrib or non-free).


  • All: only the stable distribution is used. Discussions are under way (independantly for DebianInstaller and cloud images) to list stable backports by default (installation of backport packages will still be manual, but updates become automatic).


  • Default for standard and AWS.
  • Custom for Azure and GCE.
  • TODO: what is the kernel on Azure and in Debian live systems ?


  • Standard systems contain all packages installed by debootstrap, plus the ones installed by tasksel.

  • Cloud systems contain all the packages installed by debootstrap. Addition of extra packages such as less and psmisc are discussed in (696154). Addition of cloud-init from wheezy-backports is discussed on the mailing list.

  • GCE images have third-party packages installed google-startup-scripts, google-compute-daemon, image-bundle (Free software).
  • TODO: How about the Debian live images ?

Non-packaged programs

  • Standard installations: none.
  • build-debian-cloud adds some startup scripts to the images it produces.

  • GCE images: Two unpackaged command-line utilities, see Cloud/GoogleComputeEngineImage.

  • TODO: Azure and Live ?

Default account


  • AWS: 379101102735/debian-wheezy-amd64-YYYYMMDD
  • Azure: ?
  • GCE: debian-7-wheezy-vYYYYMMDD (project ID: debian-cloud)