Compare commits

..

1 Commits

2 changed files with 12 additions and 10 deletions

View File

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

View File

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