Custom init scripts

back to index

Note: this applies to ABC SBC release 5.4 and higher.

For special cases, when some command or script is needed to be started inside the ABC SBC or CCM container on every container start, there is the possibility to provide custom pre- and post-init scripts that will be started automatically.

The pre-init part is started during container boot, after networking is up, but before other services.

The post-init part is started at the end of initialization of SBC/CCM specific parts. Note that some other services may be still started after that.

To provide custom script(s) to be started, there are two directories under the /data directory of the container. If the /data is used as persistent, it allows those custom script to survive even container replacement.


All scripts found in those directories, that are set as executable, will be started in alphanumerical order.