startx/runner-nodejs repository overview

⁠STARTX Docker-Images Repository

This project is a collection of application or services containers ready to execute or embed your application as part of a building process (docker⁠, podman⁠, s2i⁠) or by running it direcly with various containers engines like docker⁠, podman⁠, dockerEE⁠, kubernetes⁠ or openshift⁠.

Each container is provided with various underlying OS version based on CentOS⁠, Fedora Linux⁠, Alpine⁠ and UBI⁠ distributions. Kubernetes⁠ and Openshift⁠ friendly, they can all be used as a s2i builder⁠ within an openshift cluster.

If you're used to work with redhat like and distribution, you would prefer start working from a container based on this distribution rather than ubuntu or debian like distributions. OS, services and application you will find in this project will be closer to your favorite distribution

Please read each container manual for more information on how you can use it in your project and start using stable or experimental services in your applications

⁠OS, Services and Applications guidelines

⁠Images flavours

• latest based on fedora rawhide see detail⁠
• fc34 based on fedora core 34 see detail⁠
• fc33 based on fedora core 33 see detail⁠
• fc32 based on fedora core 32 see detail⁠
• fc31 based on fedora core 31 see detail⁠
• fc30 based on fedora core 30 see detail⁠
• fc29 based on fedora core 29 see detail⁠
• fc28 based on fedora core 28 see detail⁠
• fc27 based on fedora core 27 see detail⁠
• fc26 based on fedora core 26 see detail⁠
• centos8 based on Centos 8 see detail⁠
• centos7 based on Centos 7 see detail⁠
• centos6 based on Centos 6 see detail⁠
• alpine3 based on Alpine 3.12 see detail⁠
• ubi8 based on RedHat UBI 8 see detail⁠

⁠For advanced users

You you want to use this repository and code to build and create locally theses containers. You can follow theses instructions to setup and working environment.

This section is usefull if you want :

• Get latest version of embedded services, applications and underlying OS
• Enhance container content by adding instruction into container(s) Dockefile before the build process
• Use this set of container and flavour to benchmark application performance

⁠Setup your working environment (mandatory)

If 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⁠.

1. Install docker and docker-compose on your environment
2. Check if you have a running docker daemon using docker --version If not try to run it using sudo docker --daemon. If docker is not installed, follow docker installation guidelines⁠
3. Check if you have docker-compose installed using docker-compose --version. If docker-compose is not installed, follow docker-compose installation guidelines⁠
4. Check if you have git installed using git --version. If git is not installed, execute sudo dnf install -yq git
5. Copy repository source locally
6. Setup a working directory with mkdir startx-docker-images; cd startx-docker-images;
7. Clone source repository with git clone https://github.com/startxfr/docker-images.git .

⁠Build all containers using docker-compose

If you want to build and run locally all the images provided in this repository, you can follow this instructions

1. Choose your flavour with git checkout ≤flavour_name>. You can use every flavour available in this repository. Default is set to master branch related to the :latest flavour
2. Create host directory to store container content with mkdir /tmp/container.
3. Start building all containers with docker-compose build. You should be on top of your working directory to run this command. It will use the docker-compose.yml file located into this directory.
4. Wait... (could take some time as you are building the complete list of services
5. Run your multi-container with docker-compose up -d
6. Look at your containers startup with docker-compose logs. You can add a service name to get logs about this specific container. You can also monitor /tmp/container/logs to see logs comming from all containers
7. Monitor containers with docker-compose ps.

⁠Run a single container

⁠Build & run a container using docker

1. Build the container using docker build -t <image_name> <path_to_Dockerfile> where image-name is the name of your future local image and_path_to_Dockerfile_ should point to the targeted service or application directory, not including the Dockefile filename
2. Run this container
3. Interactively with docker run -it <image_name> where image_name is the name of your previously created image name. If you add a second parameter, you can run a particular command instead of the default entrypoint. Could be usefull when you add /bin/bash to get a shell running into the container
4. As a daemon with docker run -d <image_name> where image_name is the name of your previously created image name.

⁠Build & run a container using docker-compose

1. Jump into the container directory you wan to build with cd <path_to_service> where path_to_service is the targeted service or application directory, not including the docker-compose.yml filename
2. Run this container
3. Interactively with docker-compose up. You should see container startup logs and escaping this command will stop the container
4. As a daemon with docker-compose up -d. You can look at your container startup and behaviour with docker-compose logs

⁠sx lib release lifecycle

You can run sx version to know witch version of the sx-lib you are running. Older environement may not be updated and stay stiked to a defined stable release.

sx-lib release is defined with the following rules