Error installing Ubuntu packages in case Docker repository already setup

[NymanRobin]

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.

[Rozzii]

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

[metal3-io-bot]

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

[Rozzii]

/remove-lifecycle stale

[metal3-io-bot]

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

[tuminoid]

/remove-lifecycle stale

[metal3-io-bot]

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

[Rozzii]

/remove-lifecycle stale
/lifecycle frozen