Overview

This document describes creating a Tibero Image to be used as a template and deploying a container using Portainer.

Method

Tibero Image

Images

• An image is required to create a container.

• An image is a concept similar to a VM template.

• The image includes the necessary environment setup such as essential Tibero packages and Linux utilities.

Dockerfile

• On the Portainer page, select Image > Build a new image.

• name: The name and version of the image.

• Web editor: The Dockerfile content to be used for the image.

Tibero Dockerfile

# OS Image
FROM rockylinux:9.3

# Signature
MAINTAINER Junsu Yoon

# Repo Update
RUN yum update -y

# Tibero Package (ncurses version:6)
RUN yum install -y gdb gcc libaio-devel 

# tools
RUN yum install -y wget file lsof zip tree iproute passwd psmisc vim
RUN yum install -y sysstat net-tools tcpdump procps
RUN yum install -y openssh-server openssh-clients

# Extra Repo Install
RUN yum install -y epel-release
# Tibero Package (ncurses version:5)
RUN yum install -y ncurses-c++-libs-6.2-10.20210508.el9_6.2.x86_64                       
RUN yum install -y ncurses-compat-libs-6.2-8.20210508.1.el9.x86_64                       
RUN yum install -y ncurses-devel-6.2-10.20210508.el9_6.2.x86_64
RUN yum remove -y epel-release

• Using rockylinux:9.3 as the OS image may cause errors related to ncurses.

• By default, ncurses6 and tinfo6 are installed. After enabling the Extra Repo, ncurses5 and tinfo5 are also installed.

• ncurses6, tinfo6: for versions 8, 9
• ncurses5, tinfo5: for versions 6, 7

• Tools that will be used by default are pre-installed.

• Once the build is complete, you can check the progress information in the output.

• If the image creation does not show a successful completion message as above, the creation has failed.
• If it fails, compare the failed step with the Dockerfile and take corrective action.

Tibero Container

Container Creation

Check the created image.

Prepare to create the container.

Enter the container name and select the image.

Interactive & TTY

• Enable this feature for terminal connection usage.

Enable Privileged mode

• For Tibero, which makes many system calls, this must be enabled.

When Privileged mode is enabled, most features are activated. However, verify the necessary items once more.

• Enable IPC_LOCK
  This is essential because Tibero performs Memory Lock.
  Related to mlock (tbcm) function.

• Enable SYS_PTRACE
  Required for using gdb.
  gdb is used when performing callstack dumps.

   

After creation, verify access to the container.

Tibero Installation

PS C:\Users\junsu-pc\Desktop\portainer_test> ls


    Directory: C:\Users\junsu-pc\Desktop\portainer_test


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----      2025-01-28   3:30 PM      483653580 tibero6-bin-FS07_CS_2005-linux64_3.10-286096-20250127144447.tar.gz
-a----      2025-11-28   9:51 AM      586777705 tibero7-bin-FS02_PS04-linux64_4.18-305874-20251124164136.tar.gz


PS C:\Users\junsu-pc\Desktop\portainer_test> docker cp .\tibero7-bin-FS02_PS04-linux64_4.18-305874-20251124164136.tar.gz tibero_test:/tmp/
Successfully copied 587MB to tibero_test:/tmp/

Use the docker cp command to copy the Tibero binary into the container. It is recommended to use a relatively recent binary.

For T6 FS06 version, confirm whether patch 141005 is applied or if it has been reflected in later versions.

[root@9a00815f7ac0 /]# cd ~
[root@9a00815f7ac0 ~]# tar -xvzf /tmp/tibero7-bin-FS02_PS04-linux64_4.18-305874-20251124164136.tar.gz 
[root@9a00815f7ac0 ~]# ls
anaconda-ks.cfg  anaconda-post.log  original-ks.cfg  tibero7

• Inside the container, extract the copied binary and then use it.

Conclusion

• You can deploy Tibero Images and Containers through the Portainer page.
• The next document will cover automatic creation and deletion of Tibero Containers using the Portainer Stack feature.

Example: Various Tibero configurations can be automated through Portainer Stack.