Pull changes from upstream and rebase for: rebuild for latest f29

OSBS can automatically bump the release number, for that
we just need to drop the label from the Dockerfile

See https://pagure.io/ContainerSIG/container-sig/issue/1

Signed-off-by: Clement Verna <cverna@tutanota.com>

Dockerfile

@@ -7,7 +7,6 @@ with all the tools needed to use source-to-image functionality while keeping \
 the image size as small as possible." \
     NAME=s2i-core \
     VERSION=0 \
-    RELEASE=4 \
     ARCH=x86_64
 
 LABEL summary="$SUMMARY" \
@@ -19,8 +18,6 @@ LABEL summary="$SUMMARY" \
       com.redhat.component="$NAME" \
       name="$FGC/$NAME" \
       version="$VERSION" \
-      release="$RELEASE.$DISTTAG" \
-      architecture="$ARCH" \
       usage="This image is supposed to be used as a base image for other images that support source-to-image" \
       maintainer="SoftwareCollections.org <sclorg@redhat.com>"
 
@@ -32,7 +29,8 @@ ENV \
     APP_ROOT=/opt/app-root \
     # The $HOME is not set by default, but some applications needs this variable
     HOME=/opt/app-root/src \
-    PATH=/opt/app-root/src/bin:/opt/app-root/bin:$PATH
+    PATH=/opt/app-root/src/bin:/opt/app-root/bin:$PATH \
+    PLATFORM="fedora"
 
 # This is the list of basic dependencies that all language container image can
 # consume.
@@ -54,6 +52,9 @@ RUN INSTALL_PKGS="bsdtar \
 # Copy extra files to the image.
 COPY ./root/ /
 
+# Create a platform-python symlink if it does not exist already
+RUN [ -e /usr/libexec/platform-python ] || ln -s /usr/libexec/system-python /usr/libexec/platform-python
+
 # Directory with the sources is set as the working directory so all STI scripts
 # can execute relative to this path.
 WORKDIR ${HOME}

Dockerfile.fedora

@@ -0,0 +1 @@
+Dockerfile

README.md

@@ -28,22 +28,23 @@ Two examples:
 * If you specify `BASH_ENV`, then all your `#!/bin/bash` scripts
 do not need to call `scl enable`.
 * If you specify `PROMPT_COMMAND`, then on execution of the
-`docker exec ... /bin/bash` command, the collection will be automatically enabled.
+`podman exec ... /bin/bash` command, the collection will be automatically enabled.
 
 *Note*:
 Executables in Software Collections packages (e.g., `ruby`)
 are not directly in a directory named in the `PATH` environment variable.
 This means that you cannot do:
 
-    $ docker exec <cid> ... ruby
+    $ podman exec <cid> ... ruby
 
 but must instead do:
 
-    $ docker exec <cid> ... /bin/bash -c ruby
+    $ podman exec <cid> ... /bin/bash -c ruby
 
 The `/bin/bash -c`, along with the setting the appropriate environment variable,
 ensures the correct `ruby` executable is found and invoked.
 
+Note: while the examples in this README are calling `podman`, you can replace any such calls by `docker` with the same arguments
 
 Usage
 ------------------------
@@ -63,7 +64,7 @@ $ make build VERSIONS=core TARGET=rhel7
 This image is available on DockerHub. To download it run:
 
 ```console
-docker pull sclorg/s2i-core-centos7
+podman pull sclorg/s2i-core-centos7
 ```
 
 To build a Base image from scratch run:
@@ -82,4 +83,5 @@ See also
 --------
 Dockerfile and other sources are available on https://github.com/sclorg/s2i-base-container.
 In that repository you also can find another variants of S2I Base Dockerfiles.
-Dockerfile for CentOS is called Dockerfile, Dockerfile for RHEL is called Dockerfile.rhel7.
+The Dockerfile for CentOS is called Dockerfile, the Dockerfile for RHEL7 is called Dockerfile.rhel7,
+the Dockerfile for RHEL8 is called Dockerfile.rhel8 and the Dockerfile for Fedora is Dockerfile.fedora.

core

@@ -0,0 +1 @@
+.

help.md

@@ -0,0 +1 @@
+README.md

root/help.1

@@ -32,7 +32,7 @@ Two examples:
 * If you specify \fB\fCBASH\_ENV\fR, then all your \fB\fC#!/bin/bash\fR scripts
 do not need to call \fB\fCscl enable\fR\&.
 * If you specify \fB\fCPROMPT\_COMMAND\fR, then on execution of the
-\fB\fCdocker exec ... /bin/bash\fR command, the collection will be automatically enabled.
+\fB\fCpodman exec ... /bin/bash\fR command, the collection will be automatically enabled.
 
 .PP
 \fINote\fP:
@@ -44,7 +44,7 @@ This means that you cannot do:
 .RS
 
 .nf
-$ docker exec <cid> ... ruby
+$ podman exec <cid> ... ruby
 
 .fi
 .RE
@@ -56,7 +56,7 @@ but must instead do:
 .RS
 
 .nf
-$ docker exec <cid> ... /bin/bash \-c ruby
+$ podman exec <cid> ... /bin/bash \-c ruby
 
 .fi
 .RE
@@ -65,6 +65,9 @@ $ docker exec <cid> ... /bin/bash \-c ruby
 The \fB\fC/bin/bash \-c\fR, along with the setting the appropriate environment variable,
 ensures the correct \fB\fCruby\fR executable is found and invoked.
 
+.PP
+Note: while the examples in this README are calling \fB\fCpodman\fR, you can replace any such calls by \fB\fCdocker\fR with the same arguments
+
 .SH Usage
 .PP
 Choose either the CentOS7 or RHEL7 base image:
@@ -93,7 +96,7 @@ This image is available on DockerHub. To download it run:
 .RS
 
 .nf
-docker pull sclorg/s2i\-core\-centos7
+podman pull sclorg/s2i\-core\-centos7
 
 .fi
 .RE
@@ -121,4 +124,5 @@ on all provided versions of s2i image.\fP
 Dockerfile and other sources are available on 
 \[la]https://github.com/sclorg/s2i-base-container\[ra]\&.
 In that repository you also can find another variants of S2I Base Dockerfiles.
-Dockerfile for CentOS is called Dockerfile, Dockerfile for RHEL is called Dockerfile.rhel7.
+The Dockerfile for CentOS is called Dockerfile, the Dockerfile for RHEL7 is called Dockerfile.rhel7,
+the Dockerfile for RHEL8 is called Dockerfile.rhel8 and the Dockerfile for Fedora is Dockerfile.fedora.

root/usr/bin/cgroup-limits

@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/libexec/platform-python
 
 """
 Script for parsing cgroup information