volker.raschek/createrepo-docker
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

docs(README): migrate from docker.io to git.cryptic.systems

Browse Source
This commit is contained in:
Markus Pesch
2025-05-12 18:19:07 +02:00
parent fc51827300
commit 23296bc971
2 changed files with 10 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@@ -2,19 +2,17 @@
[![Docker Pulls](https://img.shields.io/docker/pulls/volkerraschek/createrepo)](https://hub.docker.com/r/volkerraschek/createrepo)
This project contains all sources to build the container image
`docker.io/volkerraschek/createrepo` and the shell script `createrepo.sh`.
This project contains all sources to build the container image `git.cryptic.systems/volker.raschek/createrepo` and the
shell script `createrepo.sh`.
The primary goal of this project is to package the binary `createrepo` as
container image to provide the functionally for CI/CD workflows or for systems
which does contains the binary.
The primary goal of this project is to package the binary `createrepo` as container image to provide the functionally
for CI/CD workflows or for systems which does contains the binary.
## createrepo.sh
The shell script `createrepo.sh` is a wrapper for the binary `createrepo`, which
is not available depending on the distribution. It starts the container image
`docker.io/volkerraschek/createrepo` in the background to call the binary. For
this reason, a container runtime like `docker` or `podman` is necessary.
The shell script `createrepo.sh` is a wrapper for the binary `createrepo`, which is not available depending on the
distribution. It starts the container image `git.cryptic.systems/volker.raschek/createrepo` in the background to call
the binary. For this reason, a container runtime like `docker` or `podman` is necessary.
### Installation
@@ -26,8 +24,8 @@ curl https://git.cryptic.systems/volker.raschek/createrepo-docker/raw/branch/mas
### Usage
The script forwards all arguments directly to the binary running inside the
container. For this reason, all arguments from the original binary can be used.
The script forwards all arguments directly to the binary running inside the container. For this reason, all arguments
from the original binary can be used.
```bash
createrepo.sh --update . # Update local repository

2
createrepo.sh
View File

@@ -4,7 +4,7 @@ set -e
CONTAINER_RUNTIME=$(which docker)
CREATEREPO_IMAGE_FULLY_QUALIFIED="docker.io/volkerraschek/createrepo:0.17.2" # renovate: datasource=docker registryUrl=https://docker.io depName=volkerraschek/createrepo
CREATEREPO_IMAGE_FULLY_QUALIFIED="git.cryptic.systems/volker.raschek/createrepo:0.17.2" # renovate: datasource=docker registryUrl=https://docker.io depName=volkerraschek/createrepo
CUSTOM_UID="${CUSTOM_UID:-"$(getent passwd "${USER}" | cut -d ':' -f 3)"}"
CUSTOM_GID="${CUSTOM_GID:-"$(getent passwd "${USER}" | cut -d ':' -f 4)"}"