chore(base): use podman replace docker

Author: duanhongyi

.woodpecker/build-linux.yml

@@ -13,8 +13,8 @@ pipeline:
   image: bash
   commands:
   - export VERSION=$([ -z $CI_COMMIT_TAG ] && echo latest || echo $CI_COMMIT_TAG)-$(sed 's#/#-#g' <<< $CI_SYSTEM_ARCH)
-  - echo $CONTAINER_PASSWORD | docker login $DRYCC_REGISTRY --username $CONTAINER_USERNAME --password-stdin > /dev/null 2>&1
-  - make clean docker-build docker-immutable-push clean
+  - echo $CONTAINER_PASSWORD | podman login $DRYCC_REGISTRY --username $CONTAINER_USERNAME --password-stdin > /dev/null 2>&1
+  - make clean build publish clean
   secrets:
   - codename
   - dev_registry

.woodpecker/manifest.yml

@@ -22,13 +22,13 @@ pipeline:
 - name: publish-manifest
   image: bash
   commands:
-  - docker run --rm
+  - podman run --rm
     -e PLUGIN_SPEC=.woodpecker/manifest.tmpl
     -e PLUGIN_USERNAME=$CONTAINER_USERNAME
     -e PLUGIN_PASSWORD=$CONTAINER_PASSWORD
     -v $(pwd):$(pwd)
     -w $(pwd)
-    plugins/manifest
+    docker.io/plugins/manifest
   secrets:
   - container_username
   - container_password

Dockerfile

@@ -1,5 +1,5 @@
 ARG BASE_LAYER
 FROM ${BASE_LAYER}
 ENV LANG C.UTF-8
-SHELL ["/bin/bash", "-c"]
+RUN ln -sf /bin/bash /bin/sh
 ENTRYPOINT ["init-stack"]

Makefile

@@ -4,7 +4,7 @@ IMAGE = "${DRYCC_REGISTRY}"/drycc/base:"${CODENAME}"-"$(shell dpkg --print-archi
 BASE_LAYER = "${IMAGE}"-prebuild
 WORK_DIR = /workspace/"${CODENAME}"
 
-SHELLCHECK_PREFIX := docker run --rm -v ${CURDIR}:/workdir -w /workdir ${DRYCC_REGISTRY}/drycc/go-dev shellcheck
+SHELLCHECK_PREFIX := podman run --rm -v ${CURDIR}:/workdir -w /workdir ${DRYCC_REGISTRY}/drycc/go-dev shellcheck
 SHELL_SCRIPTS = $(shell find . -name '*.sh') $(wildcard debootstrap/*/rootfs/*/bin/*) $(wildcard debootstrap/*/rootfs/*/sbin/*)
 
 SHELL=/bin/bash -o pipefail
@@ -15,22 +15,22 @@ clean:
 mkimage:
 	./scripts/mkimage.sh minbase "${CODENAME}"
 
-docker-import:
-	@docker import ${WORK_DIR}.tar.gz ${BASE_LAYER}
+podman-import:
+	@podman import ${WORK_DIR}.tar.gz ${BASE_LAYER}
 
-docker-build: mkimage docker-import
-	@docker build . \
+podman-build: mkimage podman-import
+	@podman build . \
 	  --tag ${IMAGE} \
 	  --build-arg BASE_LAYER=${BASE_LAYER} \
 	  --file Dockerfile
 
-docker-immutable-push: test-style	build
-	@docker push "${IMAGE}"
+podman-immutable-push: test-style	build
+	@podman push "${IMAGE}"
 	@echo -e "\\033[32m---> Build image $codename complete, enjoy life...\\033[0m"
 
-build: docker-build
+build: podman-build
 
-publish: docker-immutable-push
+publish: podman-immutable-push
 
 test: test-style
 

…pt/apt.conf.d/docker-autoremove-suggests …apt.conf.d/container-autoremove-suggestsdebootstrap/bookworm/rootfs/etc/apt/apt.conf.d/docker-autoremove-suggests renamed to debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/container-autoremove-suggests debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/docker-autoremove-suggests renamed to debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/container-autoremove-suggests

@@ -1,4 +1,4 @@
-# Since Docker users are looking for the smallest possible final images, the
+# Since Container users are looking for the smallest possible final images, the
 # following emerges as a very common pattern:
 
 #   RUN apt-get update \

…m/rootfs/etc/apt/apt.conf.d/docker-clean …ootfs/etc/apt/apt.conf.d/container-cleandebootstrap/bookworm/rootfs/etc/apt/apt.conf.d/docker-clean renamed to debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/container-clean debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/docker-clean renamed to debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/container-clean

@@ -1,9 +1,9 @@
-# Since for most Docker users, package installs happen in "docker build" steps,
-# they essentially become individual layers due to the way Docker handles
+# Since for most Container users, package installs happen in "podman build" steps,
+# they essentially become individual layers due to the way Container handles
 # layering, especially using CoW filesystems.  What this means for us is that
 # the caches that APT keeps end up just wasting space in those layers, making
 # our layers unnecessarily large (especially since we'll normally never use
-# these caches again and will instead just "docker build" again and make a brand
+# these caches again and will instead just "podman build" again and make a brand
 # new image).
 
 # Ideally, these would just be invoking "apt-get clean", but in our testing,
@@ -14,6 +14,3 @@ APT::Update::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb /var/cache/apt/a
 
 Dir::Cache::pkgcache "";
 Dir::Cache::srcpkgcache "";
-
-# Note that we do realize this isn't the ideal way to do this, and are always
-# open to better suggestions (https://github.com/docker/docker/issues).

…s/etc/apt/apt.conf.d/docker-gzip-indexes …tc/apt/apt.conf.d/container-gzip-indexesdebootstrap/bookworm/rootfs/etc/apt/apt.conf.d/docker-gzip-indexes renamed to debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/container-gzip-indexes debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/docker-gzip-indexes renamed to debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/container-gzip-indexes

@@ -1,4 +1,4 @@
-# Since Docker users using "RUN apt-get update && apt-get install -y ..." in
+# Since Container users using "RUN apt-get update && apt-get install -y ..." in
 # their Dockerfiles don't go delete the lists files afterwards, we want them to
 # be as small as possible on-disk, so we explicitly request "gz" versions and
 # tell Apt to keep them gzipped on-disk.

…s/etc/apt/apt.conf.d/docker-no-languages …tc/apt/apt.conf.d/container-no-languagesdebootstrap/bookworm/rootfs/etc/apt/apt.conf.d/docker-no-languages renamed to debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/container-no-languages debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/docker-no-languages renamed to debootstrap/bookworm/rootfs/etc/apt/apt.conf.d/container-no-languages

@@ -1,4 +1,4 @@
-# In Docker, we don't often need the "Translations" files, so we're just wasting
+# In Container, we don't often need the "Translations" files, so we're just wasting
 # time and space by downloading them, and this inhibits that.  For users that do
 # need them, it's a simple matter to delete this file and "apt-get update". :)
 

debootstrap/bookworm/rootfs/usr/sbin/initctl

@@ -1,6 +1,6 @@
 #!/bin/sh
 
-# For most Docker users, "apt-get install" only happens during "docker build",
+# For most Container users, "apt-get install" only happens during "podman build",
 # where starting services doesn't work and often fails in humorous ways. This
 # prevents those failures by stopping the services from attempting to start.
 

debootstrap/bookworm/rootfs/usr/sbin/policy-rc.d

@@ -1,6 +1,6 @@
 #!/bin/sh
 
-# For most Docker users, "apt-get install" only happens during "docker build",
+# For most Container users, "apt-get install" only happens during "podman build",
 # where starting services doesn't work and often fails in humorous ways. This
 # prevents those failures by stopping the services from attempting to start.