May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-159) "Run Image" wizard forgets volume paths [EBZ#490366]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-159?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-159: ------------------------------ Story Points: 2 > "Run Image" wizard forgets volume paths [EBZ#490366] > ---------------------------------------------------- > > Key: ERT-159 > URL: https://issues.jboss.org/browse/ERT-159 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) > > > Created attachment 260557 > The problem > On Windows when I try to run an image again, all my inputs are correctly loaded from saved configuration, except valumes' mappings(see attachment). My guess is that run configuration is saved AFTER the paths are transformed(i.e. from C:\your\path to /C/your/path) and when loading the configuration the paths are not transformed back. I was able to confirm that on Mac OS everything works fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-159) "Run Image" wizard forgets volume paths [EBZ#490366]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-159?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-159: ------------------------------ Sprint: devex #114 May 2017 > "Run Image" wizard forgets volume paths [EBZ#490366] > ---------------------------------------------------- > > Key: ERT-159 > URL: https://issues.jboss.org/browse/ERT-159 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) > > > Created attachment 260557 > The problem > On Windows when I try to run an image again, all my inputs are correctly loaded from saved configuration, except valumes' mappings(see attachment). My guess is that run configuration is saved AFTER the paths are transformed(i.e. from C:\your\path to /C/your/path) and when loading the configuration the paths are not transformed back. I was able to confirm that on Mac OS everything works fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-155) Expose DockerContainerConfig#labels() in API [EBZ#485936]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-155?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-155: ------------------------------ Story Points: 1 > Expose DockerContainerConfig#labels() in API [EBZ#485936] > --------------------------------------------------------- > > Key: ERT-155 > URL: https://issues.jboss.org/browse/ERT-155 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > This method is implemented in DockerContainerConfig but not exposed in the API (it was implemented for Linux Tools 4.2.1 which did not allow for API changes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-155) Expose DockerContainerConfig#labels() in API [EBZ#485936]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-155?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-155: ------------------------------ Sprint: devex #114 May 2017 > Expose DockerContainerConfig#labels() in API [EBZ#485936] > --------------------------------------------------------- > > Key: ERT-155 > URL: https://issues.jboss.org/browse/ERT-155 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > This method is implemented in DockerContainerConfig but not exposed in the API (it was implemented for Linux Tools 4.2.1 which did not allow for API changes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-155) Expose DockerContainerConfig#labels() in API [EBZ#485936]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-155?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-155: ------------------------------ Sprint: (was: devex #114 May 2017) > Expose DockerContainerConfig#labels() in API [EBZ#485936] > --------------------------------------------------------- > > Key: ERT-155 > URL: https://issues.jboss.org/browse/ERT-155 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > This method is implemented in DockerContainerConfig but not exposed in the API (it was implemented for Linux Tools 4.2.1 which did not allow for API changes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-154) Allow for specifying labels when running a container [EBZ#485913]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-154?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-154: ------------------------------ Story Points: 3 > Allow for specifying labels when running a container [EBZ#485913] > ----------------------------------------------------------------- > > Key: ERT-154 > URL: https://issues.jboss.org/browse/ERT-154 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) > > > Labels can be specified on the container when it is created. The wizard/launcher could also provide this feature in the UI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-156) Docker host ip cannot be copied to clipboard from anywhere [EBZ#487035]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-156?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-156: ------------------------------ Story Points: 1 > Docker host ip cannot be copied to clipboard from anywhere [EBZ#487035] > ----------------------------------------------------------------------- > > Key: ERT-156 > URL: https://issues.jboss.org/browse/ERT-156 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) > > > It would be nice if you could copy the docker host ip from somewhere. > Currently when you create a docker connection to a docker host (using Docker Machine on Mac or similar), in Docker Explorer, you see the url next to the connection name. But there is no way to copy the ip. > Currently it's not listed in the connection properties in Properties view either. I think this would be the easiest place to get it - at least show it in the Properties view so it's ready for copying to clipboard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-163) Support the '--privileged' option when running an image [EBZ#492229]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-163?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-163: ------------------------------ Sprint: devex #114 May 2017 > Support the '--privileged' option when running an image [EBZ#492229] > -------------------------------------------------------------------- > > Key: ERT-163 > URL: https://issues.jboss.org/browse/ERT-163 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22193) Can't deploy locally built docker images

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22193: ---------------------------------- [~fbricon] sorry for the late reply. Can you confirm that the work being done by Roland around support for auth credentials covers this issue, too ? > Can't deploy locally built docker images > ---------------------------------------- > > Key: JBIDE-22193 > URL: https://issues.jboss.org/browse/JBIDE-22193 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift, upstream > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > I can't deploy locally built docker images, pushed to the CDK docker registry, to OpenShift > Trying to adapt the steps from https://github.com/redhat-developer-tooling/openshift-vagrant#how-to-run-... to Eclipse, I can't seem to be able to deploy anything > Here's what the CLI generates from > {quote} > eval "$(vagrant service-manager env docker)" > $ oc login 10.1.2.2:8443 -u openshift-dev -p devel > Login successful. > $ oc new-project my-ghost > Now using project "my-ghost" on server "https://10.1.2.2:8443". > $ docker pull ghost > $ docker tag ghost hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost > $ docker login -u openshift-dev -p `oc whoami -t` -e foo(a)bar.com hub.openshift.rhel-cdk.10.1.2.2.xip.io > $ docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost > $ oc new-app --image-stream=ghost --name=ghost > $ oc expose service ghost --hostname=my-ghost-blog.rhel-cdk.10.1.2.2.xip.io > {quote} > Deployment Config > {noformat} > { > "kind" : "DeploymentConfig", > "apiVersion" : "v1", > "metadata" : { > "name" : "ghost", > "namespace" : "my-ghost", > "selfLink" : "/oapi/v1/namespaces/my-ghost/deploymentconfigs/ghost", > "uid" : "a7dafee5-03c8-11e6-82b7-525400ac6ae1", > "resourceVersion" : "29849", > "creationTimestamp" : "2016-04-16T11:45:02Z", > "labels" : {"app" : "ghost"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftNewApp"} > }, > "spec" : { > "strategy" : { > "type" : "Rolling", > "rollingParams" : { > "updatePeriodSeconds" : 1, > "intervalSeconds" : 1, > "timeoutSeconds" : 600, > "maxUnavailable" : "25%", > "maxSurge" : "25%" > } > }, > "triggers" : [ > {"type" : "ConfigChange"}, > { > "type" : "ImageChange", > "imageChangeParams" : { > "automatic" : true, > "containerNames" : ["ghost"], > "from" : { > "kind" : "ImageStreamTag", > "namespace" : "my-ghost", > "name" : "ghost:latest" > }, > "lastTriggeredImage" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8" > } > } > ], > "replicas" : 1, > "selector" : { > "app" : "ghost", > "deploymentconfig" : "ghost" > }, > "template" : { > "metadata" : { > "labels" : { > "app" : "ghost", > "deploymentconfig" : "ghost" > }, > "annotations" : { > "openshift.io/container.ghost.image.entrypoint" : "[\"/entrypoint.sh\",\"npm\",\"start\"]", > "openshift.io/generated-by" : "OpenShiftNewApp" > } > }, > "spec" : { > "volumes" : [{"name" : "ghost-volume-1"}], > "containers" : [{ > "name" : "ghost", > "image" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8", > "ports" : [{ > "containerPort" : 2368, > "protocol" : "TCP" > }], > "volumeMounts" : [{ > "name" : "ghost-volume-1", > "mountPath" : "/var/lib/ghost" > }], > "terminationMessagePath" : "/dev/termination-log", > "imagePullPolicy" : "Always" > }], > "restartPolicy" : "Always", > "terminationGracePeriodSeconds" : 30, > "dnsPolicy" : "ClusterFirst" > } > } > }, > "status" : { > "latestVersion" : 1, > "details" : {"causes" : [{"type" : "ConfigChange"}]} > } > } > {noformat} > Image Stream > {noformat} > { > "kind" : "ImageStream", > "apiVersion" : "v1", > "metadata" : { > "name" : "ghost", > "namespace" : "my-ghost", > "selfLink" : "/oapi/v1/namespaces/my-ghost/imagestreams/ghost", > "uid" : "98a32494-03c8-11e6-82b7-525400ac6ae1", > "resourceVersion" : "29842", > "creationTimestamp" : "2016-04-16T11:44:37Z", > "annotations" : {"openshift.io/image.dockerRepositoryCheck" : "2016-04-16T11:44:37Z"} > }, > "status" : { > "dockerImageRepository" : "172.30.178.20:5000/my-ghost/ghost", > "tags" : [{ > "tag" : "latest", > "items" : [{ > "created" : "2016-04-16T11:44:37Z", > "dockerImageReference" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8", > "image" : "sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8" > }] > }] > } > } > {noformat} > When following these steps in Eclipse, no deployment occurs. Going to the web console et clicking deploy on the Deployment, no image is found to deploy. > {quote} > - Clone https://github.com/burrsutter/cdk_helloworlds/ > - import java/wildflyswarm_helloworld as a Maven Project > - Run a Maven build (Run As > Maven > package) > - Edit Dockerfile: replace `FROM rhel7` with `FROM centos` > - right click on Dockerfile > Run As > Docker Image build > - Select `CDK Server Adapter at localhost` connection > - Repository Name : hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm > - from OpenShift explorer, create a fredo project > - In OpenShift explorer, right-click the fredo project and Deploy Docker Image... > - select hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm:latest for the image > - swarm as resource name > - click next > - Deployment configuration & scalability page displays, click next > - click add route button, click finish > - resources are created, but no deployment happens > {quote} > Here are the resources created from Eclipse: > Deployment Config > {noformat} > { > "metadata" : { > "name" : "swarm", > "namespace" : "fredo", > "selfLink" : "/oapi/v1/namespaces/fredo/deploymentconfigs/swarm", > "uid" : "2e9d1df4-03cc-11e6-82b7-525400ac6ae1", > "resourceVersion" : "30206", > "creationTimestamp" : "2016-04-16T12:10:17Z", > "labels" : {"deploymentconfig" : "swarm"}, > "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"} > }, > "spec" : { > "strategy" : { > "type" : "Rolling", > "rollingParams" : { > "updatePeriodSeconds" : 1, > "intervalSeconds" : 1, > "timeoutSeconds" : 600, > "maxUnavailable" : "25%", > "maxSurge" : "25%" > } > }, > "triggers" : [ > {"type" : "ConfigChange"}, > { > "type" : "ImageChange", > "imageChangeParams" : { > "automatic" : true, > "containerNames" : ["swarm"], > "from" : { > "kind" : "ImageStreamTag", > "name" : "swarm:latest" > } > } > } > ], > "replicas" : 1, > "selector" : {"deploymentconfig" : "swarm"}, > "template" : { > "metadata" : {"labels" : {"deploymentconfig" : "swarm"}}, > "spec" : { > "containers" : [{ > "name" : "swarm", > "image" : "fredo/swarm:latest", > "ports" : [{ > "name" : "8080-tcp", > "containerPort" : 8080, > "protocol" : "TCP" > }], > "terminationMessagePath" : "/dev/termination-log", > "imagePullPolicy" : "Always" > }], > "restartPolicy" : "Always", > "terminationGracePeriodSeconds" : 30, > "dnsPolicy" : "ClusterFirst" > } > } > }, > "apiVersion" : "v1", > "kind" : "DeploymentConfig" > } > {noformat} > Image Stream > {noformat} > { > "metadata" : { > "name" : "swarm", > "namespace" : "fredo", > "selfLink" : "/oapi/v1/namespaces/fredo/imagestreams/swarm", > "uid" : "2e42dfc8-03cc-11e6-82b7-525400ac6ae1", > "resourceVersion" : "30202", > "creationTimestamp" : "2016-04-16T12:10:16Z", > "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"} > }, > "spec" : {"dockerImageRepository" : "hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm"}, > "status" : {"dockerImageRepository" : "172.30.178.20:5000/fredo/swarm"}, > "apiVersion" : "v1", > "kind" : "ImageStream" > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20737) On Linux, non-root user is not able to use auto-detect to access running Docker instance

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20737: --------------------------------------------- i'm not really following what the problem is - if the user does not have access to the docker connection then eclipse can't be expected to have such access either. Is this not working as intended ? > On Linux, non-root user is not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.4.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016