46 lines
1.8 KiB
Org Mode
46 lines
1.8 KiB
Org Mode
:PROPERTIES:
|
|
:ID: cce/podman
|
|
:ROAM_REFS: https://podman.io/
|
|
:ROAM_ALIASES: Podman
|
|
:END:
|
|
#+TITLE: use PodMan for local container builds
|
|
#+ARCOLOGY_KEY: cce/podman
|
|
#+ARCOLOGY_ALLOW_CRAWL: t
|
|
#+PROPERTY: header-args :mkdirp yes :results none
|
|
#+PROPERTY: header-args:yaml :tangle roles/endpoint/tasks/podman.yml
|
|
#+CCE_ANSIBLE: podman
|
|
#+CCE_PRIORITY: 20
|
|
#+CCE_PREDICATE: (cce/using-linux)
|
|
#+filetags: :CCE:
|
|
|
|
I've been using the [[https://github.com/docker/docker-ce][first-party Docker Community Edition]] repository for a while because I was incensed when [[id:fedora_linux][Fedora Linux]] broke the "distro-supported" packages to use their own registries, and made it needlessly difficult to override to use the Docker Hub registries, and then Docker failed to port to the [[https://ask.fedoraproject.org/t/help-needed-docker-issue-with-cgroup-v2/4166/3][CGroup V2 hierarchy which Fedora enabled in version 32]]. Well, fine, you win. When I updated [[id:fedora_linux][Fedora Linux]] to version 33, my Docker containers all lost networking and I can't be fucked to continue fighting with this. Congratulations Red Hat on another happy customer!
|
|
=podman-docker= is good enough to get my =Dockerfiles= to build, while my server still runs =docker-ce=. I'll have to address that elsewhere, [[id:d63a6190-d8ac-4555-b74f-8c3e7e05519b][CCE Server]] is largely an [[id:09fa0674-ad3b-43c5-8d7c-6b532346a772][open thread]] still.
|
|
|
|
#+begin_src yaml
|
|
- name: purge docker-ce
|
|
dnf:
|
|
state: absent
|
|
name:
|
|
- docker-ce
|
|
- docker-ce-cli
|
|
tags:
|
|
- podman
|
|
|
|
- name: purge docker-ce repository
|
|
file:
|
|
state: absent
|
|
path: /etc/yum.repos.d/docker-ce.repo
|
|
tags:
|
|
- podman
|
|
|
|
- name: podman is installed
|
|
dnf:
|
|
state: installed
|
|
name:
|
|
- podman
|
|
- podman-docker
|
|
tags:
|
|
- podman
|
|
#+end_src
|