Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
i am running CoreOS inside vagrant and want to use docker in this way, after i shut down vagrant, i changed the vm name to be shorter one, then i run vagrant up, firstly, i found authentication failure problem:
then i press Ctrl+C to interrupt it, then i run vagrant ssh in the folder, this time, the system ask me for password.
but i have never set such a password, so what is the default passord for CoreOS? or how can i login to this OS which is running inside vagrant?
btw, the image of coreos is downloaded from http://beta.release.core-os.net/amd64-usr/
some people said the reason system ask for password is the the authentication of public key fails, but why it fails?
vagrant ssh-keys shows:
now i cannot login to coreos even from vbox gui:
some debug message of vagrant up:
Edit 1
seems this problem have something to do with the ssh key, but why the default ssh key failed? and how to solve this problem now?
There is no password authentication available for CoreOS, you must use either the default ssh key as specified in the documentation, or equip a cloud config file with a new key.
Quote from the docs: CoreOS Vagrant Docs
You can provide cloud-config data to your CoreOS Vagrant VM by editing the user-data file inside of the cloned directory.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 days ago.
Improve this question
can't run docker run command and docker desktop is stopped...
i tried reinstalling and upgraded wsl 1 to 2
Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/create": open //./pipe/docker_engine: The system cannot find the file specified. See 'docker run --help'.
The error suggests that docker is not running or properly installed, if you installed it, check the following.
From the search bar, type "Turn Windows features on or off" and make sure you enable the following:
Windows subsystem for Linux
virtual machine platform
windows hypervisor platform
You may also check the PATH of the docker if it is properly added in the environment variable.
From the search bar type "Edit the system environment variable" then click on "Environment variable" in the bottom right corner then under the System variable section choose "path" in the "variable" column then "edit"
A new window will open. Make sure that the following path is added
C:\Program Files\Docker\Docker\resources\bin
If you have done all these steps. You should make sure that the docker desktop app is running, then try to run docker commands.
If the problem still persists, you may uninstall the app and reinstall it again and it should work
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 11 months ago.
Improve this question
I'm trying to install hue by helm on local kubernetes, using minikube context. Installation go well, but at the end I have to find hue running on http://minikube:32284, but on the browser I obtain "Impossible to find IP Address of the minikube server". Whitch is the problem?
I have only to do:
minikube service hue
This is because my cluster k8s don't run in local, but run in virtual environment created by docker. So when I search in local I can't find minikube. The command minikube service create a tunnel that expose the service to the external environment
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I have a two part question:
first is that can anyone please tell me the command lines to execute in docker to start building a container and vm?
second is i have already built a VM using docker but the problem is whenever the building of VM reaches the stage where it written WAITING FOR VM TO BOOT it's stuck there and the error of HYPERVISOR IS NOT RUNNING comes even when the HYPER-V MACHINE MANAGEMENT is on automatic and running.
So please, help me get rid of this problem.
To create a VM which will run docker, use docker-machine: copy docker-machine-Windows-x86_64.exe as docker-machine.exe anywhere you want.
docker-machine create -d virtualbox
docker-machine start
But Make sure you have removed the Windows feature HyperV, as it is not compatible with VirtualBox/VMWare.
Or use the Hyper-V driver. You have to chose one or the other.
See "Getting Docker running on Windows 10"
as it turns out, HyperV and VirtualBox will not run together side-by-side in 64 bit modes. And Scott's blog post about rebooting to a hypervisorlaunchtype off mode of Windows 8.1 worked flawlessly for Windows 10.
So I didn't have to un-install the HyperV feature, but as it turns out, I did have to disable HyperV
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have a server with centos running rails application each time when I reboot my system I have doing following tasks manually. How to enable all the following tasks in start up
To stop and start my nginx I am using
sudo fuser -k 80/tcp # to stop
sudo /opt/nginx/sbin/nginx # to start
And to start my postgresql I am using following command
service postgresql-9.2 start/stop/restart
Once I connect my server using ssh and try some postgresql command ill get error as
postgresql-9.2: unrecognized service
To avoid this am using command
export PATH=/usr/pgsql-9.2/bin:$PATH
And then ill use postgresql(Doing export command each time when I connect through ssh).
And I am using ghost blog facing same issue whenever I reboot my server I need to run following command to start my ghost blog
NODE_ENV=production forever start index.js
How to solve all these. Can any one help
You can add the process in your init script that is at /etc/init.d/
.You can further read run script on startup
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
When I launch it with sudo /etc/init.d/dse start it seems to work. It returns:
Starting DSE daemon dse
DSE daemon starting with Hadoop and Solr disabled (edit /etc/default/dse to enable)
But when I try to connect to the tutorial "Test Cluster" (so localhost) with opscenter (on a distant machine but with port 8888 shared), I got this error:
Error creating cluster: Unable to connect to cluster
And if I check the health of dse with sudo /etc/init.d/dse status: I got:
dse dead but pid file exists
Original post:
The console or /var/log/cassandra/output.log will likely contain something like this (where nodename1 is whatever you named your node):
Error: Exception thrown by the agent : java.net.MalformedURLException: Local host name unknown: java.net.UnknownHostException: nodename1: nodename1
Same as problem on starting cassandra, basically you need to make sure that the hostname you are using can be resolved (by putting it into /etc/hosts).