[
https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi...
]
Marián Labuda edited comment on JBIDE-22134 at 4/8/16 10:00 AM:
----------------------------------------------------------------
[~jcantrill] For example, I was experiencing this issue when I tried to deploy
openshift/wildfly-90-centos7 image to OpenShift. When inspecting the docker image the
following is present in container config:
{code}"ExposedPorts": {
"8080/tcp": {}
},{code}
{code}"Env": [
"PATH=/opt/app-root/src/bin:/opt/app-root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"STI_SCRIPTS_URL=image:///usr/libexec/s2i",
"STI_SCRIPTS_PATH=/usr/libexec/s2i",
"HOME=/opt/app-root/src",
"BASH_ENV=/opt/app-root/etc/scl_enable",
"ENV=/opt/app-root/etc/scl_enable",
"PROMPT_COMMAND=. /opt/app-root/etc/scl_enable",
"WILDFLY_VERSION=9.0.2",
"WILDFLY_VERSION_BIN=9.0.2.Final",
"MAVEN_VERSION=3.3.3"
],{code}
I think those are (meta)data we are using in wizard and somehow, sometimes they are not
present in Deploy Docker Image to OpenShift wizard. Table containing env. vars and ports
are empty in the wizard. This is happening when an image is already pulled locally. But so
far, as I mentioned, I was not able to find a reliable way to reproduce it. I was not
experiencing this when I was trying to use an image which has not been pulled yet. But it
does not necessary mean it is a cause of it or it has something to do with that, but it
could be related.
was (Author: mlabuda):
[~jcantrill] For example, I was experiencing this issue when I tried to deploy
openshift/wildfly-90-centos7 image to OpenShift. When inspecting the docker image the
following is present:
{code}"ExposedPorts": {
"8080/tcp": {}
},{code}
{code}"Env": [
"PATH=/opt/app-root/src/bin:/opt/app-root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"STI_SCRIPTS_URL=image:///usr/libexec/s2i",
"STI_SCRIPTS_PATH=/usr/libexec/s2i",
"HOME=/opt/app-root/src",
"BASH_ENV=/opt/app-root/etc/scl_enable",
"ENV=/opt/app-root/etc/scl_enable",
"PROMPT_COMMAND=. /opt/app-root/etc/scl_enable",
"WILDFLY_VERSION=9.0.2",
"WILDFLY_VERSION_BIN=9.0.2.Final",
"MAVEN_VERSION=3.3.3"
],{code}
I think those are (meta)data we are using in wizard and somehow, sometimes they are not
present in Deploy Docker Image to OpenShift wizard. Table containing env. vars and ports
are empty in the wizard. This is happening when an image is already pulled locally. But so
far, as I mentioned, I was not able to find a reliable way to reproduce it. I was not
experiencing this when I was trying to use an image which has not been pulled yet. But it
does not necessary mean it is a cause of it or it has something to do with that, but it
could be related.
Sometimes docker image data are not shown in Deploy to OpenShift
wizard
-----------------------------------------------------------------------
Key: JBIDE-22134
URL:
https://issues.jboss.org/browse/JBIDE-22134
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Labels: docker, openshift_v3
Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard.
Environment variables, exposed ports etc. Unfortunately I don't have a way to
reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a
local docker image (image already pulled) to OpenShift, environment variables and exposed
ports are empty, even though when using an image which has not been pulled yet, I have not
spotted this at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)