[SRU] adsys 0.14.1

Bug #2059756 reported by Jean-Baptiste Lallement
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
adsys (Ubuntu)
Fix Released
High
Unassigned
Jammy
Incomplete
Undecided
Unassigned
Mantic
Fix Committed
Undecided
Unassigned
golang-1.22 (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
Mantic
Fix Released
Undecided
Unassigned

Bug Description

[context]
ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules.

Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release.

Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases.

This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment.

Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers.

At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance.

[references]
LP: https://launchpad.net/ubuntu/+source/adsys
LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
GitHub: https://github.com/ubuntu/adsys/
GH Bugs: https://github.com/ubuntu/adsys/issues
Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/
Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html

[changes]
Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog
 * New features
   * New policies:
     - Add mount / network shares policy manager
     - Add AppArmor policy manager
     - Support multiple AD backends and implement Winbind support
     - Add system proxy policy manager
     - Add certificate policy manager for machines
     - Add adsysctl policy purge command to purge applied policies
     - Full documentation
     - Full end to end automated test suite.

 * Enhancements
  * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine
  * Expose Ubuntu Pro status in the "status" command
  * Update scripts manager creation
  * List Pro policy types in service status output
  * Warn when Pro-only rules are configured
  * Use systemd via D-Bus instead of systemctl commands
  * Add placeholder notes for entry types
  * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos
  * Rework policy application sync strategy
  * Print logs when policies are up to date
  * Update policy definitions to include dconf key for dark mode background
  * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
  * Allow sssd backend to work without ad_domain being set (LP: #2054445)
  * Update apport hook to include journal errors and package logs

 * Bug fixes
  * Fix policy update failing when GPT.INI contains no version key
  * Fix object lookup for users having a FQDN as their hostname
  * Support special characters in domains when parsing sssd configuration
  * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
  * Ensure empty state for dconf policy
  * Handle case mismatches in GPT.INI file name
  * Ensure GPO URLs contain the FQDN of the domain controller
  * Add runtime dependency on nfs-common

 * Other
  * Updates to latest versions of Go (fixing known Go vulnerabilities)
  * Updates to latest versions of the Go dependencies
  * Updates and improvements to CI and QoL
  * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version

Dependencies:
* Build-dep: golang-go (>= 2:1.22~)

* Dependencies to backport to 22.04:
  * golang-go >= 2:1.22
  * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise)
  * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise)
  * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text=

[test plan]
# Process
Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active directory environment (https://github.com/ubuntu/adsys/actions/workflows/e2e-tests.yaml).

The team applied the following quality criteria:
 * All changes are thoroughly reviewed and approved by core team members before integration.
 * Each change is thoroughly tested at the unit, integration and system levels.
 * All the tests pass in all supported architectures.
 * All bugs fixed in this release must have a link to the pull request that fixes them.
 * All bug fixes and new features are verified in a system by executing automated or manual tests. Most of these tests are automated and executed in the autopkgtest suite. Tests that are not automated are executed manually.
 * New and existing features are tested in a real Active Directory environment.
 * There are no unfixed bugs tagged "blocker" on the milestone.

# Packaging QA
To prepare the release to 22.04, the following procedures will be completed to ensure quality:
 * All autopkgtests pass.
 * The package does not break when upgrading.
 * The binary is identical to the CI build, with only Debian packaging changes.
 * The copyrights and changelog are up to date.
 * An upgrade test from the previous package version has been performed using apt install/upgrade.

# Code sanity
Code sanity checks are performed automatically on each build. They verify:
 * Code linting
 * Go module files are up to date
 * Generated files are up to date
 * Any binary in the project builds
 * Vulnerabilities
Example report: https://github.com/ubuntu/adsys/actions/runs/6955264244

# Code coverage
 * Code coverage is computed on every build and a report generated.
 * Codecov report: https://app.codecov.io/gh/ubuntu/adsys
 * Coverage as of today: 90.78%

# Manual tests
 1. Configure your machine with AD, with a correctly configured SSSD and KRB5. AD user should be able to log in (https://canonical-adsys.readthedocs-hosted.com/en/latest/how-to/set-up-adsys/)
 2. Install admx and adml files on your AD controller (https://canonical-adsys.readthedocs-hosted.com/en/latest/how-to/set-up-ad/)
 3. Configure some Group Policies in the AD server (https://canonical-adsys.readthedocs-hosted.com/en/latest/how-to/use-gpo/)
 4. Install ADSys, reboot the machine and login in as an AD user.
 5. Ensure that the configuration done in the AD server is reflected on the Ubuntu machine.

[where problems could occur]
For AD users:
 * ADSys can prevent authentication of AD users if some policies can't be applied or fail to apply properly
 * Note: The categories of bugs we've identified typically revolve around Active Directory setup or network configuration. Extensive and detailed logging of both SSSD and ADSys aids in resolving these issues promptly.

 * For local users, no impact will occur.

Notes:
* Recommends python-cepces and python-requests-gssapi are referenced in https://bugs.launchpad.net/ubuntu/+source/python-cepces/+bug/2048514
* The other recommends ubuntu-proxy-manager is referenced in https://bugs.launchpad.net/ubuntu/+source/ubuntu-proxy-manager/+bug/2048232

description: updated
description: updated
Changed in adsys (Ubuntu):
importance: Undecided → High
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Changed in adsys (Ubuntu):
status: New → Fix Released
description: updated
Revision history for this message
Gabriel Nagy (gabuscus) wrote :
tags: added: patch
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "golang-1.22_1.22.1-1~ubuntu22.04.1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

Changed in golang-1.22 (Ubuntu):
status: New → Fix Released
description: updated
Revision history for this message
Gabriel Nagy (gabuscus) wrote :
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in adsys (Ubuntu Jammy):
status: New → Confirmed
Changed in golang-1.22 (Ubuntu Jammy):
status: New → Confirmed
description: updated
description: updated
Revision history for this message
Gabriel Nagy (gabuscus) wrote :

Attached debdiff for Go 1.22 backport to Mantic

Revision history for this message
Gabriel Nagy (gabuscus) wrote :

Attached debdiff for adsys 0.14.1 backport to Mantic

Changed in adsys (Ubuntu Mantic):
status: New → Confirmed
Changed in golang-1.22 (Ubuntu Mantic):
status: New → Confirmed
Revision history for this message
Robie Basak (racb) wrote :

Currently the version of adsys in Mantic is 0.13.1ubuntu0.1, which is lower than the version in Jammy Unapproved. What's your plan for Mantic and/or users upgrading to Mantic please?

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We plan to SRU the stack to Mantic and align all the supported releases on the same version.

Revision history for this message
Robie Basak (racb) wrote :

OK, thanks. I guess we can review the Jammy upload for now then on the assumption that the Mantic upload won't have substantial changes until it arrives in the queue.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Yes, the package is ready to upload to Mantic, and it is strictly the same.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

golang 1.22 is now in mantic NEW queue and adsys 0.14.1~23.10 is in the unapproved queue (the only change on the last one is that I adapted the debdiff to not remove the rebuild upload changelog entry).

Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Jean-Baptiste, or anyone else affected,

Accepted golang-1.22 into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/golang-1.22/1.22.2-2~23.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in golang-1.22 (Ubuntu Mantic):
status: Confirmed → Fix Committed
tags: added: verification-needed verification-needed-mantic
Changed in adsys (Ubuntu Mantic):
status: Confirmed → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Jean-Baptiste, or anyone else affected,

Accepted adsys into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~23.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Jean-Baptiste, or anyone else affected,

Accepted golang-1.22 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/golang-1.22/1.22.2-2~22.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in golang-1.22 (Ubuntu Jammy):
status: Confirmed → Fix Committed
tags: added: verification-needed-jammy
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (adsys/0.14.1~23.10)

All autopkgtests for the newly accepted adsys (0.14.1~23.10) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

adsys/0.14.1~23.10 (amd64, arm64, armhf, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/mantic/update_excuses.html#adsys

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Gabriel Nagy (gabuscus) wrote :

I've successfully performed validation on mantic with adsys and dependencies from proposed, with a Windows Server 2019 AD Controller. I've tested the specific cases for the following bugs and confirm the fixes:
  * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
  * Allow sssd backend to work without ad_domain being set (LP: #2054445)

Otherwise I've performed a full set of all combinations of policy apply (user, machine, pro enabled, pro disabled) for the full suite of policy managers and confirm they work as expected.

NB: The autopkgtest failure was due to not specifying the full path to the Go executable in the test runner (because we use Go from golang-1.22 which doesn't put the `go` binary in $PATH). We fixed that and uploaded the package with the autopkgtest fix as version 0.14.1~23.10.1.

tags: added: verification-done-mantic
removed: verification-needed-mantic
Revision history for this message
Steve Langasek (vorlon) wrote (last edit ):

I have begun reviewing the adsys upload in the jammy unapproved queue. The review is not yet complete, but I am sending my partial review notes for the desktop team to respond to.

First, I note that since this is a new upstream version, there are a number of bugs referenced in the changelog that are not going to go through SRU verification. Per https://wiki.ubuntu.com/StableReleaseUpdates#Bug_references_in_changelogs, please update the descriptions of these bugs to indicate this explicitly, so it is clear as part of the SRU review process that these are net SRU bugs that are missing the SRU bug template.

The bugs referenced in the .changes are:
LP: #2012371 LP: #2020682 LP: #2024377 LP: #2037270 LP: #2037271 LP: #2044112 LP: #2049061 LP: #2051363 LP: #2054445

Then, I have reviewed the changes to the Debian packaging in this package. I have prioritized this initially because as a rule, exceptions for new upstream versions of software do not extend to packaging changes since those pertain to distro integration and not upstream code. My observations:

- debian/prerm: this change is simply incorrect and clearly untested, because dpkg NEVER calls a prerm script with an argument of 'purge'; 'purge' is only ever given as an argument to a postrm script. This change to the prerm should be reverted, in devel and in the SRU in the queue; and brought back only after there is a verified implementation with a test case.
- apport hook changes: no runtime impact. accepted.
- addition of a new empty /var/lib/adsys dir: accepted.
- installation of additional adsys python module: accepted.
- lintian overrides change: no runtime impact. accepted.
- build dep on golang-1.22-go: golang-go in jammy is 1.18. accepted.
- added build-deps: accepted.
- krb5/winbind as an alternative to sssd: why? not discussed in the changelog and the integration of krb5+winbind directly, vs sssd, is strictly inferior.
- addition of Depends: apparmor - unusual; packages which integrate with apparmor do not in general depend on it. Basically irrelevant anyway since snapd does depend on apparmor and is mandatory. But I think this should be dropped in devel.
- additional of dependency on nfs-common: since nfs mounts are not used by default, and are overall uncommon in AD environments, I believe this better fits the policy definition of a Recommends rather than a Depends. However, adsys is opt-in and in either case will pull in nfs-common by default so I will not block on this.

I will follow up with any review comments on the upstream changes incrementally.

Changed in adsys (Ubuntu Jammy):
status: Confirmed → Incomplete
Revision history for this message
Gabriel Nagy (gabuscus) wrote :

Hi Steve,

Thanks for the review. Here are my responses for the not-accepted packaging bits:

- debian/prerm: thank you for catching this, I don't know how it slipped through, I guess it was all the false encouragement given by packages in the wild that employ the same (broken) prerm workflow. I've opened a PR to revert this upstream https://github.com/ubuntu/adsys/pull/1026 -- I don't think it adds much value to have this working (and it was not explicitly documented in the changelog either, so I'm happy with removing the broken code, as it never worked)
- krb5/winbind as an alternative to sssd: this was explicitly requested by paying customers with specific requirements related to cross-domain forest setups which could not be satisfied by sssd directly -- it's documented (albeit in a terse manner, only mentioning winbind) in the 0.10.0 changelog
- addition of Depends: apparmor: opted for this because the apparmor policy manager subprocesses "apparmor_parser" (ref: https://github.com/ubuntu/adsys/blob/b20890f78bd55d5b5c90d77af61d17eb31f40b77/internal/policies/apparmor/apparmor.go#L82) -- happy to drop it if you think it's the best practice
- additional of dependency on nfs-common: opted for a "Depends" here because adsys could apply a nfs mount policy which would fail hard if nfs-common were not installed -- I would've gone for "Recommends" in case of a soft warning

Thanks,
Gabriel

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

> - krb5/winbind as an alternative to sssd: this was explicitly requested by paying customers with specific
> requirements related to cross-domain forest setups which could not be satisfied by sssd directly -- it's
> documented (albeit in a terse manner, only mentioning winbind) in the 0.10.0 changelog

I haven't looked at the specifics of winbind + adsys, or whether one could pick one or the other at runtime, but indeed, sssd is not able to integrate well with cross-domain AD forests. I wrote about winbind in such environments in the server guide[1].

1. https://ubuntu.com/server/docs/choosing-an-integration-method

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

@Steve, thanks for the first part of your review.

Can you provide the rest of your review so we can do a single upload that addresses all your comments?

Revision history for this message
Utkarsh Gupta (utkarsh) wrote :

Hello,

golang-1.22-go looks good, I've tested the package from -proposed and it seems to build just fine. A snip from the successful testing:

[...]
Get:56 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 git-man all 1:2.34.1-1ubuntu1.11 [955 kB]
Get:57 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 git amd64 1:2.34.1-1ubuntu1.11 [3165 kB]
Get:58 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 golang-1.22-src all 1.22.2-2~22.04 [19.8 MB]
Get:59 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 golang-1.22-go amd64 1.22.2-2~22.04 [26.0 MB]
Get:60 http://archive.ubuntu.com/ubuntu jammy/main amd64 libbtrfs0 amd64 5.16.2-1 [12.0 kB]
Get:61 http://archive.ubuntu.com/ubuntu jammy/main amd64 libbtrfs-dev amd64 5.16.2-1 [47.3 kB]
[...]

Can we please move that to -updates? It's blocking some other customer work we have. Many thanks.

Revision history for this message
Chris Halse Rogers (raof) wrote :

(out of band) Additionally, Utkarsh has validated that the golang-1.22 packages in jammy-proposed correctly build docker.io, and golang-1.22 from mantic has correctly built the adsys in mantic.

As golang-1.22 a new package in Jammy and Mantic and hence low regression risk, and in the absence of any other test plan for the golang-1.22 packages (:P), I'm releasing golang-1.22 for jammy and mantic.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package golang-1.22 - 1.22.2-2~22.04

---------------
golang-1.22 (1.22.2-2~22.04) jammy; urgency=medium

  * Backport golang 1.22 to jammy (LP: #2059756)
  * Build with Go 1.20
    - d/control{,.in}: use golang-1.20-go in Build-Depends
    - d/rules: use /usr/lib/go-1.20/bin/go to set GOROOT_BOOTSTRAP path

 -- Gabriel Nagy <email address hidden> Mon, 22 Apr 2024 14:49:00 +0300

Changed in golang-1.22 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package golang-1.22 - 1.22.2-2~23.10

---------------
golang-1.22 (1.22.2-2~23.10) mantic; urgency=medium

  * Backport to Mantic (LP: #2059756)
  * Build with Go 1.20
    + d/control{,.in}: use golang-1.20-go in Build-Depends
    + d/rules: use /usr/lib/go-1.20/bin/go to set GOROOT_BOOTSTRAP path

 -- Gabriel Nagy <email address hidden> Tue, 30 Apr 2024 15:39:36 +0300

Changed in golang-1.22 (Ubuntu Mantic):
status: Fix Committed → Fix Released
Revision history for this message
Chris Halse Rogers (raof) wrote : Update Released

The verification of the Stable Release Update for golang-1.22 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Utkarsh Gupta (utkarsh) wrote :
Download full text (9.6 KiB)

Thank you, Chris. I can confirm that Jammy Go 1.22 works nicely so far -

$ lxc launch ubuntu-daily:jammy docker-io --vm
Creating docker-io
Starting docker-io

$ lxc shell docker-io
root@docker-io:~# apt update

root@docker-io:~# ls
docker-doc_24.0.7-0ubuntu4~22.04.1_all.deb docker.io_24.0.7-0ubuntu4~22.04.1_amd64.deb snap
root@docker-io:~# apt install ./*.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'docker-doc' instead of './docker-doc_24.0.7-0ubuntu4~22.04.1_all.deb'
Note, selecting 'docker.io' instead of './docker.io_24.0.7-0ubuntu4~22.04.1_amd64.deb'
The following additional packages will be installed:
  bridge-utils containerd dns-root-data dnsmasq-base pigz runc ubuntu-fan
Suggested packages:
  ifupdown aufs-tools cgroupfs-mount | cgroup-lite debootstrap docker-buildx docker-compose-v2 rinse zfs-fuse
  | zfsutils
The following NEW packages will be installed:
  bridge-utils containerd dns-root-data dnsmasq-base docker-doc docker.io pigz runc ubuntu-fan
0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 46.7 MB/78.2 MB of archives.
After this operation, 288 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 /root/docker-doc_24.0.7-0ubuntu4~22.04.1_all.deb docker-doc all 24.0.7-0ubuntu4~22.04.1 [2325 kB]
Get:2 /root/docker.io_24.0.7-0ubuntu4~22.04.1_amd64.deb docker.io amd64 24.0.7-0ubuntu4~22.04.1 [29.1 MB]
Get:3 http://archive.ubuntu.com/ubuntu jammy/universe amd64 pigz amd64 2.6-1 [63.6 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 bridge-utils amd64 1.7-1ubuntu3 [34.4 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 runc amd64 1.1.12-0ubuntu2~22.04.1 [8405 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 containerd amd64 1.7.12-0ubuntu2~22.04.1 [37.8 MB]
Get:7 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 dns-root-data all 2023112702~ubuntu0.22.04.1 [5136 B]
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 dnsmasq-base amd64 2.90-0ubuntu0.22.04.1 [374 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy/universe amd64 ubuntu-fan all 0.12.16 [35.2 kB]
Fetched 46.7 MB in 11s (4128 kB/s)
Preconfiguring packages ...
Selecting previously unselected package pigz.
(Reading database ... 56810 files and directories currently installed.)
Preparing to unpack .../0-pigz_2.6-1_amd64.deb ...
Unpacking pigz (2.6-1) ...
Selecting previously unselected package bridge-utils.
Preparing to unpack .../1-bridge-utils_1.7-1ubuntu3_amd64.deb ...
Unpacking bridge-utils (1.7-1ubuntu3) ...
Selecting previously unselected package runc.
Preparing to unpack .../2-runc_1.1.12-0ubuntu2~22.04.1_amd64.deb ...
Unpacking runc (1.1.12-0ubuntu2~22.04.1) ...
Selecting previously unselected package containerd.
Preparing to unpack .../3-containerd_1.7.12-0ubuntu2~22.04.1_amd64.deb ...
Unpacking containerd (1.7.12-0ubuntu2~22.04.1) ...
Selecting previously unselected package dns-root-data.
Preparing to unpack .../4-dns-root-data_2023112702~ubuntu0.22.04.1_all.deb ....

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.