Minishift/CDK getsockopt: connection refused ()
Good day
Referring to https://developers.redhat.com/products/cdk/hello-world/#fndtn-windows
Having: CDK v3.6.0-1, minishift v1.24.0, Virtualbox v5.2.6, Windows 10
When running cmd minishift start from Windows PowerShell, Minishift VM is running, but getting the below errors. I've disabled Windows F/W settings as well
Starting OpenShift cluster .......................................................Error during
'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --base-dir
/var/lib/minishift/base --image
'registry.access.redhat.com/openshift3/ose-${component}:v3.10.45'
--public-hostname 192.168.99.100 --routing-suffix 192.168.99.100.nip.io err
: exit status 1 output
E1126 06:58:05.268672 2423 run_self_hosted.go:542] API server
error: Get https://192.168.99.100:8443/healthz?timeout=32s: dial tcp
192.168.99.100:8443: getsockopt: connection refused () Error: timed out waiting for the condition
Any help please?
openshift minishift redhat-containers
asked Nov 26 '18 at 12:07
NicNic
26114
add a comment |
Good day
Referring to https://developers.redhat.com/products/cdk/hello-world/#fndtn-windows
Having: CDK v3.6.0-1, minishift v1.24.0, Virtualbox v5.2.6, Windows 10
When running cmd minishift start from Windows PowerShell, Minishift VM is running, but getting the below errors. I've disabled Windows F/W settings as well
Starting OpenShift cluster .......................................................Error during
'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --base-dir
/var/lib/minishift/base --image
'registry.access.redhat.com/openshift3/ose-${component}:v3.10.45'
--public-hostname 192.168.99.100 --routing-suffix 192.168.99.100.nip.io err
: exit status 1 output
E1126 06:58:05.268672 2423 run_self_hosted.go:542] API server
error: Get https://192.168.99.100:8443/healthz?timeout=32s: dial tcp
192.168.99.100:8443: getsockopt: connection refused () Error: timed out waiting for the condition
Any help please?
openshift minishift redhat-containers
asked Nov 26 '18 at 12:07
NicNic
26114
add a comment |
Good day
Referring to https://developers.redhat.com/products/cdk/hello-world/#fndtn-windows
Having: CDK v3.6.0-1, minishift v1.24.0, Virtualbox v5.2.6, Windows 10
When running cmd minishift start from Windows PowerShell, Minishift VM is running, but getting the below errors. I've disabled Windows F/W settings as well
Starting OpenShift cluster .......................................................Error during
'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --base-dir
/var/lib/minishift/base --image
'registry.access.redhat.com/openshift3/ose-${component}:v3.10.45'
--public-hostname 192.168.99.100 --routing-suffix 192.168.99.100.nip.io err
: exit status 1 output
E1126 06:58:05.268672 2423 run_self_hosted.go:542] API server
error: Get https://192.168.99.100:8443/healthz?timeout=32s: dial tcp
192.168.99.100:8443: getsockopt: connection refused () Error: timed out waiting for the condition
Any help please?
openshift minishift redhat-containers
asked Nov 26 '18 at 12:07
NicNic
26114
Good day
Referring to https://developers.redhat.com/products/cdk/hello-world/#fndtn-windows
Having: CDK v3.6.0-1, minishift v1.24.0, Virtualbox v5.2.6, Windows 10
When running cmd minishift start from Windows PowerShell, Minishift VM is running, but getting the below errors. I've disabled Windows F/W settings as well
Starting OpenShift cluster .......................................................Error during
'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --base-dir
/var/lib/minishift/base --image
'registry.access.redhat.com/openshift3/ose-${component}:v3.10.45'
--public-hostname 192.168.99.100 --routing-suffix 192.168.99.100.nip.io err
: exit status 1 output
E1126 06:58:05.268672 2423 run_self_hosted.go:542] API server
error: Get https://192.168.99.100:8443/healthz?timeout=32s: dial tcp
192.168.99.100:8443: getsockopt: connection refused () Error: timed out waiting for the condition
Any help please?
openshift minishift redhat-containers
openshift minishift redhat-containers
asked Nov 26 '18 at 12:07
NicNic
26114
asked Nov 26 '18 at 12:07
NicNic
26114
edited Nov 26 '18 at 12:29
Nic
asked Nov 26 '18 at 12:07
NicNic
26114
asked Nov 26 '18 at 12:07
NicNic
26114
asked Nov 26 '18 at 12:07
NicNic
26114
26114
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is known issue with Minishift, respectively oc-cluster-up which Minishift uses under the hood. Unfortunately I am not aware of any fix or nice workaround for it. From my experience there are however several aspects which contributes to this failure: slow machine and slow network. You can try to be connected via cable not WiFi and assign more CPUs to Minishift VM. Other tip which might help is to enable image caching in Minishift which might speed the start a little bit.
answered Feb 4 at 15:32
Andreas GajdosikAndreas Gajdosik
363
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53480795%2fminishift-cdk-getsockopt-connection-refused%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is known issue with Minishift, respectively oc-cluster-up which Minishift uses under the hood. Unfortunately I am not aware of any fix or nice workaround for it. From my experience there are however several aspects which contributes to this failure: slow machine and slow network. You can try to be connected via cable not WiFi and assign more CPUs to Minishift VM. Other tip which might help is to enable image caching in Minishift which might speed the start a little bit.
answered Feb 4 at 15:32
Andreas GajdosikAndreas Gajdosik
363
add a comment |
This is known issue with Minishift, respectively oc-cluster-up which Minishift uses under the hood. Unfortunately I am not aware of any fix or nice workaround for it. From my experience there are however several aspects which contributes to this failure: slow machine and slow network. You can try to be connected via cable not WiFi and assign more CPUs to Minishift VM. Other tip which might help is to enable image caching in Minishift which might speed the start a little bit.
answered Feb 4 at 15:32
Andreas GajdosikAndreas Gajdosik
363
add a comment |
This is known issue with Minishift, respectively oc-cluster-up which Minishift uses under the hood. Unfortunately I am not aware of any fix or nice workaround for it. From my experience there are however several aspects which contributes to this failure: slow machine and slow network. You can try to be connected via cable not WiFi and assign more CPUs to Minishift VM. Other tip which might help is to enable image caching in Minishift which might speed the start a little bit.
answered Feb 4 at 15:32
Andreas GajdosikAndreas Gajdosik
363
This is known issue with Minishift, respectively oc-cluster-up which Minishift uses under the hood. Unfortunately I am not aware of any fix or nice workaround for it. From my experience there are however several aspects which contributes to this failure: slow machine and slow network. You can try to be connected via cable not WiFi and assign more CPUs to Minishift VM. Other tip which might help is to enable image caching in Minishift which might speed the start a little bit.
answered Feb 4 at 15:32
Andreas GajdosikAndreas Gajdosik
363
answered Feb 4 at 15:32
Andreas GajdosikAndreas Gajdosik
363
answered Feb 4 at 15:32
Andreas GajdosikAndreas Gajdosik
363
answered Feb 4 at 15:32
Andreas GajdosikAndreas Gajdosik
363
363
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53480795%2fminishift-cdk-getsockopt-connection-refused%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
