~codemouse92/livecd-rootfs/+git/livecd-rootfs:hirsute-hyperv-manifest

Last commit made on 2021-08-20
Get this branch:
git clone -b hirsute-hyperv-manifest https://git.launchpad.net/~codemouse92/livecd-rootfs/+git/livecd-rootfs
Only Jason C. McDonald can upload to this branch. If you are Jason C. McDonald please log in for upload directions.

Branch merges

Branch information

Name:
hirsute-hyperv-manifest
Repository:
lp:~codemouse92/livecd-rootfs/+git/livecd-rootfs

Recent commits

4a994fb... by Jason C. McDonald

Generate manifest for HyperV desktop images

Manifests are necessary for candidate checking in the
CPC automated workflow for building and publishing
HyperV desktop images. (#1940136)

9d03006... by Michael Hudson-Doyle

releasing package livecd-rootfs version 2.719.1

6270e4d... by Michael Hudson-Doyle

Merge branch 'sru-hirsute-lp1926732' into ubuntu/hirsute

57f126a... by Michael Hudson-Doyle

fix version number for initial SRU

dc09909... by Thomas Bechtold

add debian/changelog entry

77d9988... by Thomas Bechtold

add configure_oci function and use it in ubuntu-oci

With that, the Dockerfile modifications[0] currently done externally
are done now here. That means that the created rootfs tarball can be
directly used within a Dockerfile to create a container from scratch:

FROM scratch
ADD livecd.ubuntu-oci.rootfs.tar.gz /
CMD ["/bin/bash"]

[0]
https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh

(cherry picked from commit a81972a58b004897bf3e5c14ff371bc2f6b5e4b8)

3ad6996... by Thomas Bechtold

Add new ubuntu-oci project

This is a copy of the ubuntu-base project.
Currently ubuntu-base is used as a base for the docker/OCI container
images. The rootfs tarball that is created with ubuntu-base is
published under [0]. That tarball is used in the FROM statement of the
Dockerfile as base and then a couple of modifications are done inside
of the Dockerfile[1].
The ubuntu-oci project will include the changes that are currently
done in the Dockerfile. With that:

1) a Dockerfile using that tarball will be just a 2 line thing:

   FROM scratch
   ADD ubuntu-hirsute-core-cloudimg-amd64-root.tar.gz /
   CMD ["/bin/bash"]

2) Ubuntu has the full control about the build process of the
docker/OCI container. No external sources (like [1]) need to be
modified anymore.
3) Ubuntu can publish containers without depending on the official
dockerhub containers[2]. Currently the containers for the AWS ECR
registry[3] use as a base[4] the official dockerhub containers. That's
no longer needed because a container just needs a Dockerfile described
in 1)

When the ubuntu-oci project has the modifications from [1] included,
we'll also update [1] to use the ubuntu-oci rootfs tarball as a base
and drop the modifications done at [1].

Note: Creating a new ubuntu-oci project instead of using ubuntu-base
will make sure that we don't break users who are currently using
ubuntu-base rootfs tarballs for doing their own thing.

[0] https://partner-images.canonical.com/core/
[1]
https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh
[2] https://hub.docker.com/_/ubuntu
[3] https://gallery.ecr.aws/ubuntu/ubuntu
[4]
https://launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+oci/ubuntu/+recipe/ubuntu-20.04

(cherry picked from commit ac4a95b9314cf1f8ce01f42016c271c0a6078372)

0502333... by Łukasz Zemczak

releasing package livecd-rootfs version 2.719

37e3826... by Łukasz Zemczak

Changelog

1d537bf... by Łukasz Zemczak

Temporarily hack in ubuntu-raspi-settings for raspi images (we should be using seeds tho).