Simple container used to build & test openshift and kubernetes scripts, using gitlabCI runner, under a container based on startx/fedora container
:latest : Fedora core rawhide + oc + kubectl + tools:fc32 : Fedora core 32 + oc + kubectl + tools:fc31 : Fedora core 31 + oc + kubectl + tools:fc30 : Fedora core 30 + oc + kubectl + tools:fc29 : Fedora core 29 + oc + kubectl + tools:fc28 : Fedora core 28 + oc + kubectl + tools:fc27 : Fedora core 27 + oc + kubectl + tools:centos8 : CentOS 8 + oc + kubectl + tools:centos7 : CentOS 7 + oc + kubectl + tools:centos6 : Centos 6 + oc + kubectl + tools:alpine3 : Alpine 3.10 + oc + kubectl + tools:ubi8 : RedHat UBI 8 + oc + kubectl + toolsIf you want to be guided on setting-up and installing various containers engines (docker, podman, s2i, dockerEE, kubernetes, openshift) you can read ours containers engines guidelines.
docker you can run docker run -it --name="service-oc" startx/runner-oc from any docker hostdocker-compose you can create a docker-compose.yml file with the following contentservice:
image: startx/runner-oc:latest
container_name: "service-oc"
volumes:
- "/tmp/container/oc/logs:/logs:z"
You can use this Dockerfile template to start a new personalized container based on this container. Create a file named Dockerfile in your project directory and copy this content inside. See docker guide for instructions on how to use this file.
FROM startx/runner-oc:latest
#... your container specifications
CMD ["/bin/sx", "run"]
This container is based on startx fedora container who came with some additional environment variable
| Variable | Type | Mandatory | Description |
|---|---|---|---|
| base image environement | see environment list | ||
| HOSTNAME | auto | auto | Container unique id automatically assigned by docker daemon at startup |
| LOG_PATH | auto | auto | default set to /var/log/oc and used as a volume mountpoint |
| Port | Description |
|---|---|
| 2002 | network port used to communicate with unoconv service |
| Container directory | Description |
|---|---|
| /logs | log directory used to record container and oc logs |
access to the running unoconv service with unoconv client unoconv -s localhost -p 2002. Change port and hostname according to your current configuration
You want to use this container and code to build and create locally this container, follow theses instructions.
This section will help you if you want to :
You must have a working environment with the source code of this repository. Read and follow how to setup your working environment to get a working directory. The following instructions assume you are at the top level of your working directory.
dockercd GitlabRunner/ocdocker build -t runner-oc .docker run -p 2002:2002 -v /logs -it runner-oc. If you add a second parameter (like /usr/bin/oc) to will run this command instead of the default entrypoint. Usefull to interact with this container (ex: /usr/bin/oc, /bin/ps -a, /bin/df -h,...)docker run -p 2002:2002 -v /logs -d runner-ocdocker-composecd GitlabRunner/ocdocker-compose up Startup logs appears and escaping this command stop the containerdocker-compose up -d. Container startup logs can be read using docker-compose logsIf you experience trouble with port already used, edit docker-compose.yml file and change port mapping
Content type
Image
Digest
sha256:37318baeb…
Size
400.1 MB
Last updated
over 1 year ago
docker pull startx/runner-oc