I'm trying to setup crc on my mac os laptop:
$ crc setup --help
Set up local virtualization and networking infrastructure for the OpenShift cluster
Usage:
crc setup [flags]
Flags:
-h, --help help for setup
-d, --vm-driver string The driver to use for the OpenShift cluster. Possible values: [hyperkit virtualbox] (default "hyperkit")
...
However, it seems the flag is ignored and it attempts to setup HyperKit:
$ crc setup -d virtualbox
INFO Checking if running as non-root
INFO Caching oc binary
INFO Setting up virtualization with HyperKit
...
The crc version:
$ crc version
crc version: 1.2.0+c2e3c0f
OpenShift version: 4.2.8 (embedded in binary)
My mac is version:
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.14.6
BuildVersion: 18G95
Any idea why the crc -d flag is ignored and it sets up crc with Hyperkit?
Support for VirtualBox was removed https://github.com/code-ready/crc/issues/838
Related
I inherited a Memgrpah 1.6.0 based project. When I try to run the docker on my M1 power Apple I get the following error message:
m1lap ~> docker run -p 7687:7687 memgraph/memgraph
WARNING: The requested image's platform (linux/amd64) does not match the
detected host platform (Linux/arm64/v8) and no specific platform was requested
You are running Memgraph v1.6.0-community
What can I do about this?
Docker support for running Memgraph on Apple M1 machines was added in Memgraph 2.2. You will need to obtain Memgraph 2.2 (or newer) and transfer your data from existing Memgraph 1.6.
I am unable to convert OS on hardware platform from Centos8 to RHEL8 with convert2rhel-0.23-1.el8.noarch.rpm, while the same works perfectly fine on Centos 8VM.
TASK - [Prepare: Checking the firmware interface type (BIOS/UEFI)] ********
CRITICAL - Conversion of UEFI systems is currently not supported
convert2rhel --no-rhsm --enablerepo RHEL8-AppStream --enablerepo RHEL8-BaseOS --enablerepo RHEL8-Supplementary
I've just install Docker on Mac OS 10.10.5 and ran Kitematic after that and got a hug error right away. This is the beginning of it, I can paste the rest if it will help
Command failed: /usr/local/bin/docker-machine -D start default,Docker
Machine Version: 0.7.0, build a650a40,Found binary path at
/usr/local/bin/docker-machine,Launching plugin server for driver
virtualbox,Plugin server listening at address 127.0.0.1:62284,()
Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,()
Calling .GetMachineName,command=start machine=default,(default)
Calling .GetState,(default) DBG | COMMAND: /usr/local/bin/VBoxManage
showvminfo default --machinereadable,(default) DBG | STDOUT:,(default)
DBG
$ docker version
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Tue Apr 26 23:44:17 2016
OS/Arch: darwin/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
$ docker info
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
$ docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default - virtualbox Stopped Unknown
I've read the Get started with Docker Machine and a local VM one more time and found I need to run eval "$(docker-machine env default)" to setup the env-var for docker on Mac OS X.
No idea what the issue is with Docker - I am trying to get the daemon up/running but can't. Here is the error I get:
➜ ~ bash --login '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'
Creating Machine default...
Running pre-create checks...
Creating machine...
(default) OUT | Creating VirtualBox VM...
(default) OUT | Creating SSH key...
(default) OUT | Starting VirtualBox VM...
Error creating machine: Error in driver during machine creation: exit status 1
Starting machine default...
exit status 1
Regenerate TLS machine certs? Warning: this is irreversible. (y/n):
Regenerating TLS certificates
Detecting the provisioner...
Error getting SSH command: Something went wrong running an SSH command!
command : cat /etc/os-release
err : exit status 255
output :
Setting environment variables for machine default...
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/
Error getting IP address: Host is not running
docker is configured to use the default machine with IP
For help getting started, check out the docs at https://docs.docker.com
Error running connection boilerplate: default is not running. Please start it
in order to use the connection settings
I am running:
Mac OSX 10.10.5
Docker version 1.9.1, build a34a1d5
VirtualBox version 5.0.10 r104061
I reinstalled the binaries via the toolbox install tool, but to no avail.
VirtualBox is giving a permissions error, so that may be the issue (I installed v4.3 but that didn't help):
/Applications/VirtualBox.app/Contents/MacOS/VMMR0.r0: The owner is not root
If this helps, here is the log output from Kitematic:
/usr/local/bin/docker-machine -D create -d virtualbox --virtualbox-memory 2048 default returned non zero exit code. Stderr: Docker Machine Version: 0.5.1 (7e8e38e) Found binary path at /usr/local/bin/docker-machine-driver-virtualbox
Any suggestions? Thanks
It appears the virtual machine isn't getting created. Start with the same command Kitematic is running to get the full debug out and then add that to your question:
/usr/local/bin/docker-machine -D create -d virtualbox --virtualbox-memory 2048 default
I updated to OSX 10.11 and problem went away. No idea why unfortunately.
I was able to resolve an issue similar.
The issue occurred when I installed docker toolbox a second time.
I uninstalled all Virtual box ethernet drivers virtual box itself and then docker toolbox.
I then recreated the boot2docker machine
docker-machine -D create -d virtualbox --virtualbox-boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v1.9.0/boot2docker.iso --virtualbox-memory 2048 default
I've installed zabbix-2.2 (LTS) from sources on my OS X Yosemite.
When I'm trying to run server by
sudo -u _www /usr/local/sbin/zabbix_server -c /usr/local/etc/zabbix_server.conf
I'm getting following error in /tmp/zabbix_server.log.
What can I do?