-
Bug
-
Resolution: Done
-
Major
-
None
-
AMQ 7.2.2.GA
-
None
It seems that even after reconfiguration of /usr/local/s2i/run script is not performed even though log doesn't contain any error messages. The container is not starting when build via S2I, specifically type: Source, docker build seems to be fine.
Copying Config files from S2I build '/opt/amq/conf/broker.ks' -> '/home/jboss/broker/etc/broker.ks' '/opt/amq/conf/broker.ts' -> '/home/jboss/broker/etc/broker.ts' '/opt/amq/conf/broker.xml' -> '/home/jboss/broker/etc/broker.xml' '/opt/amq/conf/jgroups-ping.xml' -> '/home/jboss/broker/etc/jgroups-ping.xml' '/opt/amq/conf/logging.properties' -> '/home/jboss/broker/etc/logging.properties' Configuring S2I run to start + /opt/amq/bin/configure_custom_config.sh /home/jboss/broker Custom Configuration file 'BROKER_XML' is disabled Custom Configuration file 'LOGGING_PROPERTIES' is disabled + '[' '' = start ']'
Notice that run script is not modified with start parameter.
➜ ~ oc get pods NAME READY STATUS RESTARTS AGE amq-config-1-w2zcb 0/1 CrashLoopBackOff 5 4m amq-config-build-1-build 0/1 Completed 0 4m ➜ ~ oc debug amq-config-1-w2zcb Defaulting container name to amq-config. Use 'oc describe pod/amq-config-1-w2zcb-debug -n dsimansk' to see all of the containers in this pod. Debugging with pod/amq-config-1-w2zcb-debug, original command: /usr/local/s2i/run Waiting for pod to start ... If you don't see a command prompt, try pressing enter. sh-4.2$ cat /usr/local/s2i/run #!/bin/sh exec $AMQ_HOME/bin/launch.sh sh-4.2$ ls -l /usr/local/s2i/run -rwxrwxr-x. 1 jboss root 40 Nov 26 14:35 /usr/local/s2i/run
Image build from dockerfile has file owner set to arbitrary user. I'm not sure if that's the main cause as the sed to add start param would complain about perms.
sh-4.2$ id uid=1000700000 gid=0(root) groups=0(root),1000700000 sh-4.2$ cat /usr/local/s2i/run #!/bin/sh exec $AMQ_HOME/bin/launch.sh start sh-4.2$ ls -l /usr/local/s2i/run -rwxrwxr-x. 1 1000700000 root 46 Nov 30 12:19 /usr/local/s2i/run