Change base image to ubi-minimal

Containerfile

@@ -1,8 +1,8 @@
-FROM registry.hub.docker.com/library/alpine:3.19.1@sha256:c5b1261d6d3e43071626931fc004f70149baeba2c8ec672bd4f27761f8e1ad6b
+FROM registry.access.redhat.com/ubi9/ubi-minimal
 
 LABEL org.opencontainers.image.authors="Adrian Riobo <ariobolo@redhat.com>"
 
-RUN apk --no-cache add openssh-client sshpass zip bash curl
+RUN microdnf install -y openssh-clients sshpass zip jq
 
 COPY lib/* entrypoint.sh /usr/local/bin/
 

Makefile

@@ -1,4 +1,4 @@
-VERSION ?= 0.0.3
+VERSION ?= 0.0.4
 CONTAINER_MANAGER ?= podman
 IMG ?= quay.io/rhqp/deliverest:v${VERSION}
 

README.md

@@ -1,12 +1,6 @@
 # deliverest
 
-Base container to acting as a delivery container for multi arch and multi platform
-
-This container implements a base pattern where it handles the execution of a binary on a target host.  
-
-Deliverest typically is a place holder for an assets (binary, script...) created for certain OS and ARCH. deliverest then will connect  
-within a target host (through ssh) and copy the asset to the target host. Then it will execute a command on the target  
-host for running the delivered asset and pick the results (if any). Finally it will cleanup everything on the target host.  
+Base container to run remotely a workload at get back the outcome from it; it uses different ENVs to control the remote execution. The workload executed remotely would be define by the command on the image inheriting from deliverest.
 
 Following diagram describes a basic usage of deliverest:
 

entrypoint.sh

@@ -3,6 +3,9 @@
 # Import libs
 source remote.sh
 
+# Default values
+TARGET_CLEANUP="${TARGET_CLEANUP:-"true"}"
+
 # Debug
 if [ "${DEBUG:-}" = "true" ]; then
     set -xuo 
@@ -42,5 +45,5 @@ if [[ ! -z "${TARGET_RESULTS+x}" ]]; then
 fi
 
 if [ "${TARGET_CLEANUP:-}" = "true" ]; then
-    $(ssh_cmd "rm -fr ${TARGET_FOLDER}")
+    $(ssh_cmd "rm -r ${TARGET_FOLDER}")
 fi