Component naming in 4g-volte-deploy-opensips.yaml causes containers to not initialize

[robdyck]

"Docker compose -f 4g-volte-deploy-opensips.yaml up" will successfully run but open5gs_init.sh was not deploying some containers. The naming of the components was resulting in a bad component name. In 4g-volte-deploy-opensips.yaml I removed all the dashes from the component name. open5gs_init.sh would no attempt to deploy the containers.

However the initialization of the containers associated with the component names failed to initialize. The container initialization file could not be found bcause of the file names didn't match the component names.

Example for smf component

/open5gs_init.sh: line 83: /mnt/smf/smf1_init.sh: No such file or directory
Deploying component: 'smf1'

9ae1caf4d886   docker_open5gs             "/bin/sh -c /open5gs…"   About an hour ago   Exited (127) 8 minutes ago                smf

[razvancrainea]

It is not clear, but did you manage to sort it out? If yes, can you post a diff that got it working, perhaps open a PR?

[robdyck]

It seems that the open5gs developers wanted to be able to introduce different vaersions. Containers under the open5gs image umbrella run open5gs_init.sh when they start. This in turn runs /mnt/smf/${COMPONENT_NAME}_init.sh. So if we name a component for example smf1 then we also need the corresponding init script - smf1_init.sh.

For non-open5gs images COMPONENT_NAME has no meaning. All containers initialize and stay up for me. Attaching a diff file for 4g-volte-deploy.yaml.

diff-4g-volte-deploy-opensips.yaml.txt