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

docker2podman: pull images from docker daemon (bp #5280) #5363

Merged
merged 2 commits into from Jun 3, 2020

Conversation

dsavineau
Copy link
Contributor

This is a manual backport of pull request #5280 done by Mergify

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the simulator.

Finally, you can contact us on https://mergify.io/

@dsavineau dsavineau changed the title [skip ci] docker2podman: pull images from docker daemon (bp #5280) docker2podman: pull images from docker daemon (bp #5280) May 13, 2020
@dsavineau
Copy link
Contributor Author

jenkins test centos-container-docker_to_podman

@dsavineau dsavineau added this to the v4.2 milestone May 13, 2020
@dsavineau dsavineau changed the title docker2podman: pull images from docker daemon (bp #5280) [skip ci] docker2podman: pull images from docker daemon (bp #5280) May 13, 2020
The docker2podman playbook only installs the podman package and updates
the systemd units with the right container_binary value.

We never pull the container image so if one service is restarted then
the container image will be pulled first before the service can start
which could cause longer downstream.

To avoid to download the container image from internet again we can just
pull it from the local docker daemon.

The container_{binding,package,service}_name variables are removed
because they are only used in the ceph-container-engine role which
isn't call in this playbook.

Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
(cherry picked from commit d38f21a)
The dashboard nodes (alertmanager, grafana, node-exporter, and prometheus)
were not manage during the docker to podman migration.

This adds the systemd container template of those services to a dedicated
file (systemd.yml) in order to include it in the docker2podman playbook.

This also adds the dashboard container images pull from docker to podman.

Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1829389

Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
(cherry picked from commit 252e78b)
@dsavineau dsavineau force-pushed the mergify/bp/stable-4.0/pr-5280 branch from 18ede8b to 298a7eb Compare May 13, 2020 19:39
@dsavineau dsavineau changed the title [skip ci] docker2podman: pull images from docker daemon (bp #5280) docker2podman: pull images from docker daemon (bp #5280) May 13, 2020
@dsavineau
Copy link
Contributor Author

jenkins test centos-container-docker_to_podman

@dsavineau dsavineau modified the milestones: v4.2, v4.1z1 May 22, 2020
@dsavineau dsavineau merged commit a97e24f into ceph:stable-4.0 Jun 3, 2020
@dsavineau dsavineau deleted the mergify/bp/stable-4.0/pr-5280 branch June 3, 2020 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant