Currently there doesn't seem to be other way how to identify the internal version of the FUSE framework in the jboss-fuse-6/fis-karaf-openshift image, other than just to run the image, wait till deployed, and inspect the log file of the corresponding pod. This returns something like the following:

...
2017-01-23 08:54:41,491 | DEBUG | FelixStartLevel  | Connection                       | 2 - org.ops4j.pax.url.mvn - 2.4.2 | Resolving [mvn:org.jboss.fuse/fuse-karaf-framework/6.2.1.redhat-084/xml/features]
...

But prior pulling the actual jboss-fuse-6/fis-karaf-openshift image, customers might want to know the version of FUSE Karaf framework beforehand, e.g. by remote inspection of the image via e.g. the skopeo tool (or issuing custom properly formatted curl request to v2 of the Docker registry to obtain the manifest for the image), thus doing something like the following:

$ skopeo inspect --raw docker://registry.access.redhat.com/jboss-fuse-6/fis-karaf-openshift | grep -o -P '[^"]+_VERSION=[^"]+'
JBOSS_IMAGE_VERSION=1.2\
JAVA_VERSION=1.8.0\
FIS_KARAF_IMAGE_VERSION=1.0\
MAVEN_VERSION=3.3.3-1.el7\
JOLOKIA_VERSION=1.3.2.redhat-1\

Therefore this RFE.

Expected result of the implementation could look e.g. like:
FUSE_KARAF_FRAMEWORK_VERSION=6.2.1.redhat-084\

(or some other variable being present in the Env section of the underlying image to serve the very same purpose).

Thank you for consideration, Jan