Following the Getting Started guide for Starting a Local Cluster in Docker https://www.cockroachlabs.com/docs/stable/start-a-local-cluster-in-docker.html. The problem is that the container immediately exits.
Tried adding tail -f /dev/null but it did not work. Though pretty sure it is not supposed to be needed.
Running on Docker for Windows
Docker version 18.09.2, build 6247962
Tried with -it flag and the error listed is
*
* WARNING: RUNNING IN INSECURE MODE!
*
* - Your cluster is open for any client that can access <all your IP addresses>.
* - Any user, even root, can log in without providing a password.
* - Any user, connecting as root, can read or write any data in your cluster.
* - There is no network encryption nor authentication, and thus no confidentiality.
*
* Check out how to secure your cluster: https://www.cockroachlabs.com/docs/v19.1/secure-a-cluster.html
*
*
* ERROR: failed to start server: could not create temp storage: could not open rocksdb instance: IO error: While fsync: a directory: Invalid argument
*
Failed running "start"
Related
I went through each step and followed the documentation here https://minikube.sigs.k8s.io/docs/drivers/docker/
When I try to run
minikube start --driver=docker
I get this error
X Exiting due to PROVIDER_DOCKER_NOT_RUNNING: "docker version --format -" exit status 1: error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version": open //./pipe/docker_engine: The system cannot find the file specified.
* Suggestion: Start the Docker service
* Documentation: https://minikube.sigs.k8s.io/docs/drivers/docker/
The documentation it references is the same one I used to set everything up to begin with. I also tried switching daemon using the command "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemon
that didn't work and I tried reset the docker settings to default and I'm still getting this error.
I was trying to running a docker image from a gitlap repository as mentioned in https://codebabel.com/ci-gitlabci-docker/
I ran the image as shown below and it started
docker run -p 5000:50000 -it registry.gitlab.com/bacdef/flaskapp:latest
* Serving Flask app "helloworld" (lazy loading)
* Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
* Debug mode: on
* Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
* Restarting with stat
* Debugger is active!
* Debugger PIN: 259-006-586
But when I try to access it via browser http://127.0.0.1:5000/ or http://localhost:5000/ or http://myip:5000/ it reply as follows
This page isn’t working 127.0.0.1 didn’t send any data.
ERR_EMPTY_RESPONSE
docker ps command output ias as follows
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
04cc5dc26ec5 registry.gitlab.com/bacdef/flaskapp:latest "python helloworld.py" 18 minutes ago Up 18 minutes 0.0.0.0:5000->50000/tcp hardcore_perlman
I am running it on a mac os.
Tried solution of similar questions like How to access webserver running in docker container from browser?, https://superuser.com/questions/1204030/cannot-access-to-http-localhost4000-after-i-map-this-port-number-to-docker but it does not work.
Can somebody please suggest what am I doing wrong?
Recently in my Google Cloud Compute Engine I have some issues with the ssh & serial console. My VM seems to "crash" about a certain time, all the programs running in this machine are not responding (docker).
I tried to reset the vm & changing os but the problem persist here is Putty Error screenshot:
I tried to connect to the machine via the serial option but it I can't login,it blocks at the login prompt. I tried many times but when i reboot the vm, it works perfectly.
EDIT :
Here is the list of the installed programs :
- Docker
- Docker-Compose
**Docker images : **
* Neo4j<br/>
* A C# program<br/>
* nginx<br/>
* CachetHQ<br/>
* PostgreSQL<br/>
* CertBot<br/>
** My machine : **
Custom, 2vCpu and 5go of memory
Here is the output of cat /proc/meminfo :
https://hastebin.com/qenowepira.http
I'm about to try to disable CachetHQ & PostgreSQL
On a Windows 7 Enterprise 64 Bit OS, I installed Erlang (otp_win64_20.0.exe) and RabbitMQ 3.6.9 (64bit) as standalone one. I have set System Variable for ERLANG_HOME. The installation was successful and RabbitMQ service is running.
But when I trying to enable rabbitmq_management, I am getting following error.
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.6.9\sbin>rabbitmq-plugins.bat enable rabbitmq_management
Plugin configuration unchanged.
Applying plugin configuration to rabbit#machinename... failed.
* Could not contact node rabbit#machinename.
Changes will take effect at broker restart.
* Options: --online - fail if broker cannot be contacted.
--offline - do not try to contact broker.
C:\Program Files\RabbitMQ Server\rabbitmq_server-3.6.9\sbin>rabbitmqctl status
Status of node rabbit#machinename ...
Error: unable to connect to node rabbit#machinename: nodedown
DIAGNOSTICS
===========
attempted to contact: [rabbit#machinename]
rabbit#machinename:
* connected to epmd (port 4369) on machinename
* epmd reports node 'rabbit' running on port 25672
* TCP connection succeeded but Erlang distribution failed
* Authentication failed (rejected by the remote node), please check the Erlang cookie
current node details:
- node name: 'rabbitmq-cli-45#machinename'
- home dir: C:\
- cookie hash: LLCyvm2Dd7VpUhtY9jxerg==
I am going through various posts in stackoverflow and still could not figure out what is the root cause of this issue with node and management plugin.
Any help to resolve this is highly appreciated.
It looks like you have problem with `erlang.cookie. It contains key that allows connecting to Erlang node. You can read more about it in official documentation, but simplest solution can be found here
Installing as a non-administrator user leaves .erlang.cookie in the wrong place
This makes it impossible to use rabbitmqctl.
Workarounds:
Run the installer as an administrator or
Copy the file .erlang.cookie manually from %SystemRoot% to %HOMEDRIVE%%HOMEPATH%.
Where %SystemRoot% is normally C:\WINDOWS\.erlang.cookie and %HOMEDRIVE%%HOMEPATH%should be something like C:\Documents and Settings\%USERNAME%\.erlang.cookie or C:\Users\%USERNAME%\.erlang.cookie
This should solve your problem.
Below is some steps a developer use to start a manual deployment for a Vitria application. Now we want to understand how to automate this process using IBM UrbanCode uDeploy.
In the multiple entries of "xauth list" output, what does the number 11 mean in "unix:11".
In $DISPLAY=localhost:11.0, what does this "11" mean? Does it related to the above "unix:11"? This localhost means my local PC or the remote server?
To automated with UCD, we will have an UCD agent running under "pyaz5b", do we still need to do all this?
I don't understand why X-Window is required here, because afterwards, the developer just runs "vdadmin" to do the deployment, not from a GUI at all.
All ids below has been changed for security reasons.
*******************************************************************************
* *
* *
* Welcome to AIX Version 7.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************
[ /users/qhwms3] :~> xauth list
uavitg04/unix:12 MIT-MAGIC-COOKIE-1 c29a18c4363b8b65c78b26bf28ec
uavitg04/unix:13 MIT-MAGIC-COOKIE-1 aaf848b52f00ab4ce30e8d58209a8
uavitg04/unix:10 MIT-MAGIC-COOKIE-1 025d33bb6094e1fac5cbb465333220
uavitg04/unix:11 MIT-MAGIC-COOKIE-1 c20ec7900e35c679f9263ed64ec8c87
[ /users/qhwms3] :~> echo $DISPLAY
localhost:11.0
[ /users/qhwms3] :~> sudo su - pyaz5b
uavitg04:/home/pyaz5b > export DISPLAY=localhost:11.0
uavitg04:/home/pyaz5b > xauth add uavitg04/unix:11 MIT-MAGIC-COOKIE-1 c20ec7900e35c679f92d641ec8c87
1) You can have multiple X servers/sessions running in a machine (either on local hardware, using a virtual server or remotely). Numbering for these servers normally start at 0; your DISPLAY variable would then be ":0" or perhaps ":0.0".
However when using X11 forwarding through SSH, the SSH daemon starts numbering at 10. So there are 4 remote sessions on your server, all with X11 forwarding enabled, numbered 10 through 13.
2) Yes. The DISPLAY variabele is used by X programs to connect to the correct X server. The MIG-MAGIC-COOKIE acts as a password so that other users cannot connect to your X session (they are accessible through sockets).
3) I can't comment on that. However, I find it odd to login with one account (qhwms3), then sudo to another account (pyaz5b) and manually add the magic cookie. Why nog login into pyaz5b directly (it does seem to have a regular shell)?
4) If you are not starting an X application, then all this is not necessary. However, some tools have a 'hidden' dependency on X; they can operate in both command line and GUI mode, the latter by specificying a command switch. So even though you are using the command line interface they are still linked against the X11 libraries and sometimes always open a connection. I can't remember right now, there was a popular tool some years ago that had this annoying habit; you couldn't run it remotely unless you had X11 forwarding on, even though you didn't need an X server.