WslRegisterDistribution failed with error: 0x80370102 - docker

WslRegisterDistribution failed with error: 0x80370102
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
When I'm trying to start my Ubuntu Machine I'm facing with this error ?
open the Hyper-V on Turn windows features on or off menu

Related

Error in driver during machine creation - docker

I'm newbie with Docker, I try to create docker machine on my windows 10 (Home ver unfort.).
1st command I use "docker-machine create -d virtualbox anewmachine" which gave me following error:
"This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory",
Then I found solution for the above error on stack, that is "docker-machine create default --virtualbox-no-vtx-check". This one seems working but ended up to the following error:
Running pre-create checks...
Creating machine...
(default) Copying C:\Users\The Kash\.docker\machine\cache\boot2docker.iso to C:\Users\The
Kash\.docker\machine\machines\default\boot2docker.iso...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
(default) Starting the VM...
(default) Check network to re-create if needed...
(default) Windows might ask for the permission to configure a dhcp server. Sometimes, such
confirmation window is minimized in the taskbar.
Error creating machine: Error in driver during machine creation: Unable to start the VM:
B:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:
VBoxManage.exe: error: Call to VidMessageSlotMap failed: Last=0xc000000d/87
(VERR_NEM_VM_CREATE_FAILED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface
IConsole
Please help me.

Docker Installation Issue on Windows 8

I am trying to install docker using DockerToolBox and followed steps from ToolBox_Install_windows but I am getting this error:
00:00:51.238278 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x1, 0x8000000000000000
00:00:51.245031 VMMDev: Guest Log: 00:00:00.019443 vminfo rtldrNativeLoad: dlopen('libdbus-1.so.3', RTLD_NOW | RTLD_LOCAL) failed: libdbus-1.so.3: cannot open shared object file: No such file or directory
00:00:51.245165 VMMDev: Guest Log: 00:00:00.019599 vminfo Error: Unable to connect to system D-Bus (1/3): D-Bus not installed
00:00:51.253561 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:56.243987 VMMDev: Guest Log: 00:00:05.021831 vminfo Error: Unable to connect to system D-Bus (2/3): D-Bus not installed
And Docker Quickstart Terminal stops with message: Waiting for an IP...
Here are some details:
DockerToolbox-19.03.1
VirtualBox-6.1.12-139181-Win
I also enabled virtualisation in BIOS.
Here are some things I tried but no luck:
Close/stop running default VM created in Oracle VM VirtualBox manager
Manually start it and close again with option Send the shutdown signal
Run Docker Quickstart Terminal again.
Same question asked previously Here but provided answer is not working.
Thanks in advance.
This same problem was faced by me. What I did
Step 1 uninstall the toolbox
Step 2 download a .exe file
Step 3 normally install it.
https://youtu.be/ntBCU7cZJ1I
Step4 restarted the system
Step 5 clicked on docker toolbox and let it wait.
The point where the it looks for ip address took a long time. And I waited patiently this time
And finally it worked

Windows 10 Pro and Docker service -- is it possible to start the Docker service later?

The problem I face is that the first time the Docker service on my Windows 10 pro computer is started at boot time, then I get all kinds of errors. Restarting the Docker service solves always the problem.
On my Windows 10 pro computer the Docker Service is started automatically. The problem is that the service starts a bit too early. I know about the Windows Fastboot but changing that I find to heavy to configure that to solve this problem.
Is there a way to configure the Docker service to start later in the Windows 10 boot sequence?
You think - make it a program that is started automatically. When I configure Docker NOT as a service, then I get all kinds of problems. The Docker system tray icon sometimes even gets the red color ...
The error messages are:
ERROR: for docker-compose_geosolschmea_1 Cannot start service
geosolschmea: driver failed programming external connectivity on
endpoint docker-compose_geosolschmea_1
(3c0302743b124c050334b9ca3fcd3c9b01a0bcfaa1d629d74f7311cb09a58833):
Error starting userland proxy: mkdir
/port/tcp:0.0.0.0:3306:tcp:172.18.0.2:3306: inpuStarting
docker-compose_jenkins_1 ... error
ERROR: for docker-compose_jenkins_1 Cannot start service jenkins:
driver failed programming external connectivity on endpoint
docker-compose_jenkins_1
(fa039afd6930afba9843b89295e1bbeab32102679964780f867df1cd13282fe0):
Error starting userland proxy: mkdir
/port/tcp:0.0.0.0:8888:tcp:172.18.0.3:8080: input/output error

Unable to connect Visual Studio to remotebuild on El Capitan VM

I have a Cordova-Ionic application on Visual Studio (Microsoft Visual Studio Community 2015, Version 14.0.25123.00 Update 2). I am able to run the app on my android phone and all is good. I want to test the app by also running it on an iPhone/iOS simulator.
I have OS X El Capitan (version 10.11.6) running as a VM on virtual box. I have been following this guide (https://taco.visualstudio.com/en-us/docs/ios-guide/) to try to test the app on apple devices. I have installed version 0.12.9 Node.js and Xcode Version 8 Beta 4. I have also installed xcode command line tools, remote agent, homebrew. I have tried running 'remotebuild test' in a terminal and it executes successfully, ending with 'taco-remote test passed.' However, this is where the problems start.
To attempt to use secure remotebuild, i run 'remotebuild certificates reset' and then 'remotebuild certificates generate' in the terminal. I see
host: noyolks-iMac.local
port: 3000
PIN: 121422
I then run 'remotebuild'. On visual studios on my windows machine, I then go to tools -> options -> tools for apache cordova -> iOS configuration. I set 'Enable remote iOS processing' to 'true', 'host' to 'noyolks-iMac.local', 'port' to '3000', 'secure mode' to 'true', 'security pin' to '121422'. However, when i press ok, i see the following error popup 'Unable to connect to remote iOS build server. Underlying exception: The remote name could not be resolved: 'noyolks-imac.local''.
I try using the IP instead in place of the host name as suggested in the guide. On OS X, i go system preferences -> network. I then see '10.0.2.15' under IP address. I go back to my windows machine. I try '10.0.2.15' in place of the 'host'. When i press ok, i see the following error popup 'An error occurred trying to acquire certificate from https://10.0.2.15.'.
Please note, I ensured that all the above was done within the 10 minutes window before the security pin expires.
Following the guide, I then tried to start the remote agent without secure mode. I run 'remotebuild --secure false'. Once again on visual studio on my windows machine, i try host 'noyolks-imac.local' first (with 'port' to '3000', 'enable remote iOS processing' to 'true', 'secure mode' to 'false') and i get the error popup 'Unable to connect to remote iOS build server. Underlying exception: The remote name could not be resolved: 'noyolks-imac.local''.
Once again, running without secure mode, i instead use the ip address in place of the host '10.0.2.15'. I get the error popup 'Unable to connect to remote iOS build server. Underlying exception: Unable to connect to the remote server'.
I have also tried a similar procedure using a friends mac book pro and have not been able to get this to work. Any help would be appreciated and please do feel free to ask for any other information you might need.
Thanks.
I'm an idiot. The problem was that I couldnt even ping my El Capitan VM. Changing the network adapter settings in virtualbox to 'bridged adapter' solved this.

Troubleshoot windows error: Failed to schedule Software Protection service for re-start at 2014-09-13T08:09:23Z. Error Code: 0x80040154

My setup:
Opertaing System: Windows 8.1
Memory: 16GB
HD: 500GB
etc. non relevant.
Issue:
I noticed the issue when my printer stopped working after a normal restart. At that point I tried to uninstall and reinstall the printer driver. The install failed.
At that point I also realized all my remote desktop connections were also failing, with not being able to find the remote host.
Here is the error I was seeing when install for the printer was failing:
can't start printer spooler service not enough resources are available to start the service
Manually trying to start the spooler service and checking in the event Viewer of windows showed that it was failing on:
Failed to schedule Software Protection service for re-start at 2014-09-13T08:09:30Z. Error Code: 0x80040154.
Further trying to restart the protection service revealed that it was failing on:
Task Scheduler service has encountered RPC initialization error in "RpcServerUseProtseq:ncacn_ip_tcp". Additional Data: Error Value: 1721.
In either case my computer had become somewhat useless as I couldn't install anything and my printer and remote desktop was broken too.
Reporting the problem just in case if someone has a similar issues.
The resolution for my problem is actually posted here, but way back so bringing it to more light:
http://social.technet.microsoft.com/Forums/windows/en-US/0c438376-1486-4ae4-9847-2de7a8767f27/task-scheduler-service-has-encountered-rpc-initialization-error-in?forum=itprovistasp
For me what worked was just to starting the prompt in adminstrator mode, running:
netsh winsock reset
and restarting my machine.
Not exactly certain of what actually fixed the issue.

Resources