182 Commits

Author SHA1 Message Date
CloudBuilder
7256eceb6c Imported 24.04.26 from noble-release pocket.
No reason for CPC update specified.
2024-02-06 16:32:58 +00:00
CloudBuilder
2aeb74e5b8 Imported 24.04.21 from noble-release pocket.
No reason for CPC update specified.
2024-01-25 08:29:11 +00:00
CloudBuilder
20cb3bceae Imported 24.04.11 from noble-release pocket.
No reason for CPC update specified.
2023-12-09 07:00:12 +00:00
CloudBuilder
c704051c30 Imported 24.04.7 from noble-release pocket.
No reason for CPC update specified.
2023-12-07 23:00:17 +00:00
CloudBuilder
7fded2fbe1 Imported 24.04.2 from noble-release pocket.
No reason for CPC update specified.
2023-10-28 05:00:12 +00:00
CloudBuilder
286484e57b Imported 23.10.52 from mantic-release pocket.
No reason for CPC update specified.
2023-10-03 14:51:09 +00:00
CloudBuilder
125ac748b0 Imported 23.10.47 from mantic-release pocket.
No reason for CPC update specified.
2023-09-27 13:51:09 +00:00
CloudBuilder
007da3a58d Imported 23.10.42 from mantic-release pocket.
No reason for CPC update specified.
2023-09-19 21:51:09 +00:00
CloudBuilder
bc9a35d654 Imported 23.10.39 from mantic-release pocket.
No reason for CPC update specified.
2023-09-19 01:51:08 +00:00
CloudBuilder
d4ec07c09e Imported 23.10.31 from mantic-release pocket.
No reason for CPC update specified.
2023-09-06 03:58:24 +00:00
CloudBuilder
18626aadcb Imported 23.10.22 from mantic-release pocket.
No reason for CPC update specified.
2023-08-26 18:51:09 +00:00
CloudBuilder
81727dfb6e Imported 23.10.21
No reason for CPC update specified.
2023-08-23 20:51:09 +00:00
CloudBuilder
8b890948c6 Imported 23.10.16
No reason for CPC update specified.
2023-08-17 16:51:09 +00:00
CloudBuilder
abc9fb0cb3 Imported 23.10.13
No reason for CPC update specified.
2023-08-10 14:51:09 +00:00
CloudBuilder
63e502da78 Imported 2.899
No reason for CPC update specified.
2023-07-11 00:51:08 +00:00
CloudBuilder
740d9307aa Imported 2.896
No reason for CPC update specified.
2023-07-07 13:59:39 +00:00
CloudBuilder
1287214409 Imported 2.890
No reason for CPC update specified.
2023-06-19 08:16:56 +00:00
Simon Poirier
98375ecc7f fix: revert upstream losetup change
Roll back some upstream changes replacing kpartx by losetup while
unstable.

reverts ada1f09b39332ec828369e0a30f2870df5c4dc3e
reverts ef146db89529fc7fbc48052e0b684f7cb95f34ee
2023-05-17 11:40:04 -04:00
CloudBuilder
57dba33aea Imported 2.835
No reason for CPC update specified.
2023-05-11 17:05:43 +00:00
CloudBuilder
9c2f1531ab Imported 2.832
The tag was already there due to package removal before the release
2023-05-05 12:02:39 +00:00
CloudBuilder
a31b54068a Imported 2.828
pkg got reverted due to kpartx/losetup problems
2023-04-19 09:12:07 +00:00
CloudBuilder
dc9b11af67 Imported 2.832
No reason for CPC update specified.
2023-04-18 05:48:08 +00:00
CloudBuilder
dcb48eae8d Imported 2.821
No reason for CPC update specified.
2023-04-08 02:48:12 +00:00
CloudBuilder
3eaf5fa5e0 Imported 2.818
No reason for CPC update specified.
2023-03-30 18:48:10 +00:00
CloudBuilder
e60564a4f7 Imported 2.817
No reason for CPC update specified.
2023-03-30 05:48:10 +00:00
CloudBuilder
aa85b9d763 Imported 2.813
No reason for CPC update specified.
2023-03-19 01:48:28 +00:00
CloudBuilder
9213b8396a Imported 2.796
Force updateafter snapd patch no longer required
2023-01-20 10:46:07 +00:00
Philip Roche
18af71ff97 fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x
There is a regression in snapd 2.58 with a fix being worked on @
https://github.com/snapcore/snapd/pull/12483. The regression was
that it was no longer possible to preseed snaps during cloud
image builds. The temporary workaround is to preseed snapd
from a downgraded channel "stable/2.57.x". To do this temporarily
we will carry a patch on CPC's fork of livecd-rootfs on all suites.

Once the fix to snapd snap is rolled out with a new 2.58.1
release then the "stable/2.57.x" will be removed and
all users with snapd from channel "stable/2.57.x" will
fall back to "stable" channel and be upgraded to 2.58.1.
2023-01-13 09:40:12 +00:00
CloudBuilder
5193bfb60f Imported 2.793
No reason for CPC update specified.
2022-11-21 23:48:18 +00:00
CloudBuilder
fc7271d42f Imported 2.789
No reason for CPC update specified.
2022-10-14 00:38:15 +00:00
CloudBuilder
cfc99a6947 Imported 2.785
No reason for CPC update specified.
2022-09-27 13:38:15 +00:00
CloudBuilder
7478fdfae8 Imported 2.772
No reason for CPC update specified.
2022-07-29 04:38:25 +00:00
CloudBuilder
2a51702ede Imported 2.759
No reason for CPC update specified.
2022-03-09 10:59:14 +00:00
CloudBuilder
77c778b8fd Imported 2.756
No reason for CPC update specified.
2022-02-14 18:59:14 +00:00
CloudBuilder
f4bc08a89d Imported 2.755
No reason for CPC update specified.
2022-02-11 03:59:14 +00:00
CloudBuilder
27eae37284 Imported 2.754
No reason for CPC update specified.
2022-02-08 22:59:13 +00:00
CloudBuilder
9ec43ee45e Imported 2.752
No reason for CPC update specified.
2022-01-28 02:59:14 +00:00
CloudBuilder
3f1e663543 Imported 2.751
No reason for CPC update specified.
2022-01-14 19:59:15 +00:00
John Chittum
9c3851d401
Mount cgroup2 type for snapd
LP: 1944004 described an issue where a libc transition caused snapd
seccomp profiles to reference a path that no longer existed, leading to
permission denied errors. The committed fix for snapd then raised an
issue where running `snapd debug seeding` would present a
preseed-system-key and seed-restart-system-key due to a mismatch
between the running kernel capabilities and the profiles being loaded by
snapd. By mounting a cgroup2 type to /sys/fs/cgroup, the capabilities
match for snapd as mounted in the chroot. This is done similarly to
live-build/functions:138-140 where apparmour and seccomp actions are
mounted after updating the buildd.
2021-09-28 16:08:55 -05:00
Łukasz 'sil2100' Zemczak
2dc48a1687 Make the UBUNTU_STORE_ARCH adjustment more fool-proof 2021-08-17 12:02:39 +02:00
Ethan Hsieh
f4312118cc functions: download snap packages with correct architecture
Have to set UBUNTU_STORE_ARCH when the architecture of host machine is
different from target machine
2021-07-08 15:16:43 +08:00
Dimitri John Ledkov
20f76e7cf8
Merge branch 'preinstalled' of git+ssh://git.launchpad.net/~xnox/livecd-rootfs into ubuntu/master 2021-04-30 17:46:20 +01:00
Dimitri John Ledkov
d5a8116428
Add support for generic preinstalled images. LP: #1923832 2021-04-26 11:04:37 +01:00
Thomas Bechtold
a81972a58b
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
2021-04-22 08:48:00 +02:00
Thomas Bechtold
ac4a95b931
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
2021-04-22 07:39:15 +02:00
Dimitri John Ledkov
096a00f404
functions: stop removing systemd-detect-virt unconditionally in undivert_grub
One can call divert_grub; replace_kernel; undivert_grub. And
replace_kernel will call into force_boot_without_initramfs, which
under certain conditions can call divert_grub &
undivert_grub. Resulting in undivert_grub called twice in a row.

When undivert_grub is called twice in a row it wipes
systemd-detect-virt binary from disk, as the rm call is unguarded to
check that there is something to divert if systemd package is
installed. And if the systemd package is not installed, it does not
check that systemd-detect-virt file is in-fact what divert_grub has
created.

Add a guard to check that systemd-detect-virt is the placeholder one,
before removing it.

LP: #1902260
2021-02-03 14:45:54 +00:00
Dimitri John Ledkov
a808b28d47
riscv64: build preinstalled riscv64 image with uboot SPL and CIDATA. 2020-12-01 17:14:40 +00:00
Sebastien Bacher
79e8f3b53e Use the target realpath to do the unmounting 2020-11-24 11:36:13 +01:00
Dimitri John Ledkov
f53a681d8a
Merge remote-tracking branch 'patviafore/use_ftpmaster_instead_of_archive_in_binary_hooks' into ubuntu/master 2020-11-19 17:36:39 +00:00
John Chittum
4f1df739f6
Debug logging information
Added context lines for debugging lines.
2020-10-26 09:22:32 -05:00