[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4159:
--------------------------------
Story Points: 5
> On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4159
> URL: https://issues.jboss.org/browse/JBDS-4159
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.3.0.GA
>
>
> On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases.
> here is the error:
> {noformat}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
> Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"]
> Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3951:
-----------------------------------
Assignee: Sudhir Verma (was: Denis Golovin)
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Sudhir Verma
> Priority: Critical
> Fix For: 10.3.0.AM2
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3951:
--------------------------------
Sprint: devex #126 January 2017
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.3.0.AM2
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23136 at 1/24/17 3:43 PM:
-------------------------------------------------------------------
[~dbocharov] [~jcantrill] I'm not all sure if I get this all right, but from the blogpost [here|https://blog.openshift.com/remotely-push-pull-container-images-opens...], that describes how to push images to the docker registry in OpenShift, it seems like the approach is to use the docker cmd line and manually tag an image:
{code}
$ docker login --username=anything --email=anyone(a)anywhere.com --password=<token> <docker registry route>
$ docker push docker-registry.192.168.121.113.xip.io:80/pushed/myimage:latest
$ docker tag 445f4be0f46f
{code}
Once this is done, oc is being use to create the image stream:
{code}
$ oc import-image myimage --from=docker-registry.192.168.121.113.xip.io:80 --confirm --insecure-repository=true
{code}
In the [source for the oc binary|https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/im...] I see oc retrieving docker images by tag and creating an imagestream for it.
I'm not aware enough of what we do but I would expect us to do the same. Are we doing the same?
was (Author: adietish):
[~dbocharov] [~jcantrill] I'm not all sure if I get this all right, but from the blogpost [here|https://blog.openshift.com/remotely-push-pull-container-images-opens...], that describes how to push images to the docker registry in OpenShift, it seems like the approach is to use the docker cmd line and manually tag an image:
{code}
$ docker login --username=anything --email=anyone(a)anywhere.com --password=<token> <docker registry route>
$ docker push docker-registry.192.168.121.113.xip.io:80/pushed/myimage:latest
$ docker tag 445f4be0f46f
{code}
In the [source for the oc binary|https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/im...] I see oc retrieving docker images by tag and creating an imagestream for it.
I'm not aware enough of what we do but I would expect us to do the same. Do we?
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23136 at 1/24/17 3:43 PM:
-------------------------------------------------------------------
[~dbocharov] [~jcantrill] I'm not all sure if I get this all right, but from the blogpost [here|https://blog.openshift.com/remotely-push-pull-container-images-opens...], that describes how to push images to the docker registry in OpenShift, it seems like the approach is to use the docker cmd line and manually tag an image:
{code}
$ docker login --username=anything --email=anyone(a)anywhere.com --password=<token> <docker registry route>
$ docker push docker-registry.192.168.121.113.xip.io:80/pushed/myimage:latest
$ docker tag 445f4be0f46f
{code}
Once this is done, oc is being used to create the image stream:
{code}
$ oc import-image myimage --from=docker-registry.192.168.121.113.xip.io:80 --confirm --insecure-repository=true
{code}
In the [source for the oc binary|https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/im...] I see oc retrieving docker images by tag and creating an imagestream for it.
I'm not aware enough of what we do but I would expect us to do the same. Are we doing the same?
was (Author: adietish):
[~dbocharov] [~jcantrill] I'm not all sure if I get this all right, but from the blogpost [here|https://blog.openshift.com/remotely-push-pull-container-images-opens...], that describes how to push images to the docker registry in OpenShift, it seems like the approach is to use the docker cmd line and manually tag an image:
{code}
$ docker login --username=anything --email=anyone(a)anywhere.com --password=<token> <docker registry route>
$ docker push docker-registry.192.168.121.113.xip.io:80/pushed/myimage:latest
$ docker tag 445f4be0f46f
{code}
Once this is done, oc is being use to create the image stream:
{code}
$ oc import-image myimage --from=docker-registry.192.168.121.113.xip.io:80 --confirm --insecure-repository=true
{code}
In the [source for the oc binary|https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/im...] I see oc retrieving docker images by tag and creating an imagestream for it.
I'm not aware enough of what we do but I would expect us to do the same. Are we doing the same?
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23136 at 1/24/17 3:41 PM:
-------------------------------------------------------------------
[~dbocharov] [~jcantrill] I'm not all sure if I get this all right, but from the blogpost [here|https://blog.openshift.com/remotely-push-pull-container-images-opens...], that describes how to push images to the docker registry in OpenShift, it seems like the approach is to use the docker cmd line and manually tag an image:
{code}
$ docker login --username=anything --email=anyone(a)anywhere.com --password=<token> <docker registry route>
$ docker push docker-registry.192.168.121.113.xip.io:80/pushed/myimage:latest
$ docker tag 445f4be0f46f
{code}
In the [source for the oc binary|https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/im...] I see oc retrieving docker images by tag and creating an imagestream for it.
I'm not aware enough of what we do but I would expect us to do the same. Do we?
was (Author: adietish):
[~dbocharov] [~jcantrill] I'm not all sure if I get this all right, but from the blogpost [here|https://blog.openshift.com/remotely-push-pull-container-images-opens...], that describes how to push images to the docker registry in OpenShift, it seems like the approach is to use the docker cmd line and manually tag an image:
{code}
$ docker login --username=anything --email=anyone(a)anywhere.com --password=<token> <docker registry route>
$ docker push docker-registry.192.168.121.113.xip.io:80/pushed/myimage:latest
$ docker tag 445f4be0f46f
{code}
In the [source for the oc binary|https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/im...] I see oc retrieving docker images by tag and creating an imagestream for it.
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23136:
------------------------------------------
[~dbocharov] [~jcantrill] I'm not all sure if I get this all right, but from the blogpost [here|https://blog.openshift.com/remotely-push-pull-container-images-opens...], that describes how to push images to the docker registry in OpenShift, it seems like the approach is to use the docker cmd line and manually tag an image:
{code}
$ docker login --username=anything --email=anyone(a)anywhere.com --password=<token> <docker registry route>
$ docker push docker-registry.192.168.121.113.xip.io:80/pushed/myimage:latest
$ docker tag 445f4be0f46f
{code}
In the [source for the oc binary|https://github.com/openshift/origin/blob/master/pkg/cmd/cli/cmd/im...] I see oc retrieving docker images by tag and creating an imagestream for it.
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months