I have attempted to install an aurora node by following the guide below:
partner-relayer-deploy
However, I am having issues. If someone could point me in the right direction that would be appreciated.
This is the first time I have used docker so perhaps I am missing something basic. However, googling and some docker youtube tutorials have not help me solve it myself.
Below is a step by step of what I have done:
Running setup.sh in gitbash shows errors but continues to install.
connection errors but continues to install
When installation is complete (75GB downloaded) I did not have docker opened so it errored as it couldn't find the daemon
Opened docker. Docker shows apps restarting
Closes setup.sh and ran again. got errors.
Additional app shown in docker
closed gitbash. Renamed 'docker-compose.yaml-mainnet' to 'docker-compose.yaml' and moved from '.contrib' folder to 'partner-relayer-deploy' folder so I could run 'docker-compose up'. Ran 'docker-compose up' got errors.
Prior to posting I have done a fresh install but am still getting the same result.
---------update-----------
I found the below issue which has prompted me to ensure my docker images are up to date
https://github.com/aurora-is-near/partner-relayer-deploy/issues/20
endpoint updated but the others were fine.
https://hub.docker.com/r/nearaurora/endpoint/tags
https://hub.docker.com/r/nearaurora/nearcore/tags
https://hub.docker.com/r/nearaurora/database/tags
I am still getting the same issue when I run setup.sh
And get the following error when I run docker-compose up
Related
When I try to startup Docker Desktop on a new M1Max, it gets a fatal error that the "Docker daemon failed to start". The last log item for the daemon is just a debug message "Calling HEAD /_ping".
I'd like to try to start the daemon manually on my Mac to see if there are better error details, but all of the docs for that mention using dockerd which isn't available on the Mac install.
Background: I just switched from an older MBP to a new M1Max. I replaced my Docker Desktop with the new version for Apple Silicon and everything started up fine. However, some of my containers were having issues on the new arch. While debugging those issues, I restarted Docker Desktop and began experiencing this issue. I've tried restarting my mac, but it just gives me the same error again. I've tried downgrading Docker Desktop to the last handful of older versions and still get the same message. The strange thing is that my log file for dockerd hasn't been touched since before I restarted Docker Desktop when I first encountered the error. It's like the daemon isn't even trying to start anymore. Any help would be greatly appreciated.
UPDATE: I just reset my Mac back to my starting point (after using the migration assistant to port my old MBP to the new). When I first install Docker Desktop for Apple Silicon, it starts up normally and everything runs fine. If I check on the dockerd logs, I can see it being written to. However, as soon as I restart Docker Desktop, I get the error mentioned above and dockerd stops writing to logs. Then, every time I try to start Docker Desktop, it errors with the message above.
do the following
clean uninstall docker either using brew/appcleaner
Manually install 4.5.0 M1 - https://docs.docker.com/desktop/mac/release-notes/
that is after manually installing ensure to uncheck automatic software update from setting
!! It worked for me !!
I am relatively new for the docker technology.
Yesterday I setup docker on windows 10 machine and ran few dockers.
Today I first used command "docker system prune" so that I can run all of it once again without any conflicts.
But now I am firing below command:
docker run --name DockerName -v /c/collections:/etc/newman -t
postman/newman:ubuntu run
"MyAPITestCollection.postman_collection.json"
--environment="MyAPITestEnvironment.postman_environment.json" --reporters="json,cli" --reporter-json-export="reports/MyAPITestReport.json"
And getting below error:
error: ENOENT: no such file or directory, open 'MyAPITestEnvironment.postman_environment.json'
I haven't made any changes to the directories or anything else.
I checked the docker desktop setup option and found that the drive on which the file is located is still showing as the shared drive.
I tried by restarting the docker desktop several times and once by rebooting the machine as well but still found same error.
Kindly requesting to help me figure out the root cause of this issue and the solution as well.
My docker network had once again become public so firewall might be preventing the file access.
I changed it to private by using below command and it ran successfully:
Set-NetConnectionProfile -interfacealias "vEthernet (DockerNAT)" -NetworkCategory Private
I'm trying to use the OpenFOAM docker image. I installed everything correctly and when I try to run OpenFOAM_Start I get the error:
Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
Error response from daemon: No such container: of_1712
Error: failed to start containers: of_1712
Error: No such container: of_1712
Stopping "default"...
Machine "default" was stopped.
Then I ran docker-machine env command and I got the error:
Error checking TLS connection: Host is not running
I would appreciate if you could help me know what is the problem and how I can solve it.
P.S. Hopefully this is not off-topic. Please let me know if I should ask this question in a different stackexchange.
I found the solution but I'm still not sure what the error above mean. As indicated in the OpenFOAM installation guide, right after installation of the docker image you should run the:
"OF_Create_Env"
shortcut on the Desktop. A shell will open and close automatically,
completing setup of the user working environment. This step is mandatory
only on the first occasion of OpenFOAM for Windows installation.
Then you can run OpenFOAM_Start again and it just works.
I took a clean machine (Windows 10 Enterprise w/out the Anniversary Update) and installed (in this order) Full IIS, Hyper-V, VS2015 Enterprise, .NET Core 1.0.1 Tooling Preview 2, Docker for Windows, Visual Studio Docker Tools, and a few other random programs.
I then opened VS2015 and created a default .NET core website. When I run (F5) all works as expected. I then right clicked on the project and went to Add->Docker Support. Now when trying to run (F5) using Docker I see this error message:
MSB4018 The "PrepareForCompile" task failed unexpectedly.
Microsoft.DotNet.Docker.CommandlineClientException: Error response
from daemon: Container ... is not running at ...
I have searched online and the only thing I can find that might explain it is that I don't think Shared Drives are working. I did set it up in Docker->Shared Drives, but when I run:
docker run --rm -v c:/Users:/data alpine ls /data
the response is empty.
Likewise when I try using busy box the directory is empty.
docker run -it -v /C/Users:/wormhole busybox
cd wormhole
ls
I have tried using Windows Desktop for Docker 1.12.1-stable and beta 26. Both have the same issue.
Some have indicated that Antivirus could cause a problem. I do have Mcafee installed, but I cannot uninstall or disable the antivirus software.
Some have suggested that passwords with unusual characters can cause this issue but that does not apply here.
I don't know that shared drives are causing the VS2015 error, but it seems like a good place to start since shared drives are broken.
I have restarted bot hdock and the computer many times, to no avail.
Any Ideas?
I had the same issue.
In order to fix it I found the container referenced by the id in the stack trace. Then I removed it:
docker rm <containerid>
When I tried running from VS 2015 again it worked. I don't know what initially caused the issue.
I just wanted to add since I also stumbled upon this issue. I had a clean Win 10 machine, and I just had to enable the "Shared Drive" setting in docker:
This may not be the actual problem that you're facing (Thankfully you fixed it!); this is just for people that may not have this enabled!
This morning I've started playing with Docker, so installed boot2docker on my Mac.
All seemed to be going well, following the Working with Docker Images documentation until I tried to create a Dockerfile to install the ruby gems.
I spent a long time banging my head against the wall as to why it couldn't connect to install the gems... then I eventually worked it out, so adding this here in case anyone else has this problem in future, as there wasn't anything on Google about it.
Turns out that, because my internet bombed out during the apt-get update command, it didn't complete the update, however running it again, docker was using the cached (incomplete) data, and so if didn't work.
The fix... Run the docker build without the cache using the command...
docker build -no-cache --tag="<vendor>/<build>:<tag>" .