[ ] Feature request
[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Documentation issue or request
I had a working environment last Friday, pulled and realized my minishift instance was kinda sick, ran my usual command to restart, ran into some issues, opted to update to the latest minishift (minishift-1.30.0-linux-amd64) and give it a try. I've tried both:
tools/bin/syndesis minishift --full-reset --install --dev --local -p syndesis
And also:
tools/bin/syndesis minishift --full-reset && tools/bin/syndesis --install --dev --local -p syndesis
In either case the install just spins waiting for Syndesis to start up as the syndesis-db image apparently cannot be pulled:
Failed to pull image "172.30.1.1:5000/openshift/postgresql@sha256:4ab2cbdae8af04eb2cddd32bb97ef249d9c592353b70b4ac7188dc0601fe980a": rpc error: code = Unknown desc = Get http://172.30.1.1:5000/v2/: dial tcp 172.30.1.1:5000: getsockopt: connection refused
I've actually been hitting this kind of behavior since minishift 1.26.1 or so, but have been working around it previously by downgrading to a version of minishift that supports --openshift-version 3.9.0 but that also doesn't seem to work for me now either.
@seanforyou23 have you been seeing this kinda stuff too?
I'm trying a second machine too. The main problem is while I wait for the installation I wind up buying used studio gear on Reverb.
I have intermittent issues if I run BlueJeans at the same time as syndesis minishift --install. I find it that the install exerts the CPU and network connections, so if I do syndesis minishift --install I find it good to go do the laundry also.
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!
Most helpful comment
I'm trying a second machine too. The main problem is while I wait for the installation I wind up buying used studio gear on Reverb.