Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error installing Ubuntu packages in case Docker repository already setup #1367

Open
NymanRobin opened this issue Mar 13, 2024 · 3 comments
Open
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@NymanRobin
Copy link
Member

In my scenario, I had previously configured the Docker apt repository following the guidelines outlined in the official documentation: Docker Installation Guide for Ubuntu.

However, a problem arises when comparing this setup with the setup in Metal3-dev-env. The Docker documentation
uses the plain key format (.asc) for the apt repository signature, whereas the Metal3-dev-env setup utilizes a binary key format (.gpt). This discrepancy results in a clash within the signature, leading to the following error during installation:

TASK [packages_installation : Add Docker Repository] ***************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: apt_pkg.Error: E:Conflicting values set for option Signed-By regarding source https://download.docker.com/linux/ubuntu/ focal: /etc/apt/keyrings/docker.asc != /etc/apt/keyrings/docker.gpg,

In the code, it can be seen that there is already two tasks addressing this particular issue, both aimed at removing outdated entries with varying apt repository structures. These tasks are flagged with TODO comments to be removed further down the line

A potential solution could be to find all apt repositories associated with the URL https://download.docker.com/linux/ubuntu/, removing all entries and enforcing the utilization of signed-by=/etc/apt/keyrings/docker.gpg.

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Mar 13, 2024
@Rozzii
Copy link
Member

Rozzii commented Mar 27, 2024

Thanks for submitting this issue.
I have hit this a few times.
/triage accepted
/kind bug

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. kind/bug Categorizes issue or PR as related to a bug. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Mar 27, 2024
@metal3-io-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 25, 2024
@Rozzii
Copy link
Member

Rozzii commented Jun 26, 2024

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: Backlog
Development

No branches or pull requests

3 participants