Continuous Delivery to Microsoft #Azure with #Docker #Container for #DevOps #Dev #Code #Cloud

To make it easy for you to deploy your application to Azure we’ve built a container that has the AzureCLI installed. We will set up a simple example showing you how to configure any deployment to Azure. If you don’t have Docker yet you can get it here

With command Docker pull microsoft/azure-cli you get the latest Container

With the command docker run -it microsoft/azure-cli you will start the Container

Now you have the latest Azure CLI in a Docker Container

From inside the Microsoft Docker Container we will make a connection to a Azure subscription, if you don’t have a Microsoft Azure subscription you
can get your free Azure trail subscription here

My Microsoft Docker Container is running.

with command Azure Login you will start the login process

Copy the url https://aka.ms/devicelogin in your browser :

Copy your code from the container login into the Device login

Click on Continue for Microsoft Azure Cross-Platform CLI Login

Login with your Microsoft Azure account of your subscription

Done !

The Microsoft Docker Container with the latest Azure CLI is connected with your Azure Subscription 😉

From here you can do a Continuous Delivery to Microsoft Azure with Docker and #Code.

With the Command Azure Lab you see I can manage my Azure Dev/Test LAB from my Docker Container 😉

Here you see my Container01 in JamesTestLAB in Azure

With the Command Azure vm start we run the Azure Container01

Now the Azure Container01 is running and started from a Microsoft Docker Container with Azure CLI

Get started with Azure CLI 2.0 Technical Docs

Have a look at CodeShip here to make it your self easy for continuous delivery on Microsoft Azure Cloud

RUN you Own #Azure DevTest Labs in the Cloud #DevOps #Science #Linux #Containers

James TestLAB

Azure DevTest Labs is a service that helps developers and testers quickly create environments in Azure while minimizing waste and controlling cost. You can test the latest version of your application by quickly provisioning Windows and Linux environments using reusable templates and artifacts. Easily integrate your deployment pipeline with DevTest Labs to provision on-demand environments. Scale up your load testing by provisioning multiple test agents, and create pre-provisioned environments for training and demos.

Get started with Microsoft Azure DevTest Labs here

It’s really easy to setup your first Azure DevTest LAB.

Just click Create.

If you click on Automation options, you can create your own json file for Automation.

JSON Script for Automation to Create a Azure DevTest LAB

Getting Started information in your Azure TestLAB

I have Created a Windows Server 2016 VM with Containers

There are a lot of Azure DevTest Artifacts

You can copy the ARM Template for Automation

Container01 VM is running in my Azure DevTest LAB 😉

Container Images Ready to use in Azure DevTest LAB

For more Microsoft Azure Devtest Labs Documentation you can find here

Microsoft #Containers for Application Development #Docker #Hyperv #ACS #DevOps #Cloud

Containers for Developers

From a developer’s desktop to a testing machine to a set of production machines, a Docker image can be created that will deploy identically across any environment in seconds. This story has created a massive and growing ecosystem of applications packaged in Docker containers, with DockerHub, the public containerized-application registry that Docker maintains, currently publishing more than 180,000 applications in the public community repository.

When you containerize an app, only the app and the components needed to run the app are combined into an “image”. Containers are then created from this image as you need them. You can also use an image as a baseline to create another image, making image creation even faster. Multiple containers can share the same image, which means containers start very quickly and use fewer resources. For example, you can use containers to spin up light-weight and portable app components – or ‘micro-services’ – for distributed apps and quickly scale each service separately. 

Because the container has everything it needs to run your application, they are very portable and can run on any machine that is running Windows Server 2016. You can create and test containers locally, then deploy that same container image to your company’s private cloud, public cloud or service provider. The natural agility of Containers supports modern app development patterns in large scale, virtualized and cloud environments.

With containers, developers can build an app in any language. These apps are completely portable and can run anywhere – laptop, desktop, server, private cloud, public cloud or service provider – without any code changes.

Containers helps developers build and ship higher-quality applications, faster.

 To begin with Windows Containers, I advice to manage them with Docker and do .NET Docker Development with Visual Studio 2017

Prerequisites: 

• One computer system (physical or virtual) running Windows Server 2016.
• Configure this system with the Windows Container feature and Docker. For a walkthrough on these steps, see Windows Containers on Windows Server.
• QuickStart Windows Containers on Windows 10
• A Docker ID, this will be used to push a container image to Docker Hub. If you do not have a Docker ID, sign up for one at Docker Cloud.

Containers 101 poster

Windows Containers Infrastructure

Microsoft Windows Container with Nano server :

Docker pull microsoft/nanoserver

Docker PS

Docker run -t -I microsoft/nanoserver

Now you are inside the Windows Container on the Nano Server

If you want a Windows Container with Nano Server and IIS running for a website checkout this Docker Pull

More Microsoft images on Docker Hub repositories

Docker run reference

Docker runs processes in isolated containers. A container is a process which runs on a host. The host may be local or remote. When an operator executes docker run, the container process that runs is isolated in that it has its own file system, its own networking, and its own isolated process tree separate from the host.

This page details how to use the docker run command to define the container’s resources at runtime

Containers can run anywhere !

 

Free Windows Server 2016 Virtual Labs – #Education #Winserv #Hyperv #Containers #Nanoserver

Gain hands-on experience with the new version of Windows Server in security, software-defined datacenter and containers, using the latest virtual labs.

Guided labs make it easy to check out what’s new without spending time and money to install and configure an environment. Using the virtual labs for Windows Server 2016 you can learn about what the new technology does and how to configure it. It’s not a video, a demo you watch, or a simulator; it’s you connecting with your browser, on your PC, to our lab for free.

When you sign in with your Microsoft account you’ll be able to access any of the individual labs in a private, sandboxed environment. It all adds up to about 6 hours of content, and you can come back later if you need to.

Check out each of these 60-minute experiences:

• Breach resistant security and Shielded VMs
• Storage Spaces Direct
• Nano Server
• Windows Server and Hyper-V Containers
• Failover clustering and rolling cluster upgrades

Example of TechNet Virtual LAB Managing Windows Server 2016 :

Virtual LAB information before you begin 😉
JUST push Launch Lab to begin.

Let the Virtual LAB Windows Server 2016 Nano Server Begin 😉

Here you go to the Microsoft Virtual Lab of Windows Server 2016

#Learning
#MVPbuzz

UPDATE #Docker Community Edition for #Windows10 playing with #Containers #Linux

Docker Windows Containers

Switch to Docker Linux Containers

Docker Linux Containers on Windows

You can connect to Docker Cloud for Swarms and Repositories

You can connect to Shared Drives for your Containers

Here you can set the IP Subnet Address for the virtual Switch for the Containers

Docker Proxy settings

Docker Computing Resources

If you have issues or troubles with Docker, the log file gives you lot of information :

Log file example :

Version: 17.03.0-ce-win1 (10300)
Channel: beta
Sha1: 05a8abd3046f3afe1
Started on: 2017/03/02 20:59:31.405
Resources: C:\Program Files\Docker\Docker\Resources
OS: Windows 10 Pro
Edition: Professional
Id: 1607
Build: 14393
BuildLabName: 14393.693.amd64fre.rs1_release.161220-1747
File: C:\Users\doubl\AppData\Local\Docker\log.txt
CommandLine: “C:\Program Files\Docker\Docker\Docker for Windows.exe”
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[20:59:31.523][GUI            ][Info   ] Starting…
[20:59:31.827][Tracking       ][Info   ] Crash report and usage statistics are enabled
[20:59:31.827][SegmentApi     ][Info   ] Usage statistic: appLaunched
[20:59:31.910][NamedPipeClient][Info   ] Sending Version()…
[20:59:31.932][NamedPipeClient][Info   ] Received response for Version
[20:59:31.932][SegmentApi     ][Info   ] Usage statistic: heartbeat
[20:59:30.145][BackendServer  ][Info   ] Started
[20:59:31.932][NamedPipeServer][Info   ] Version()
[20:59:31.932][NamedPipeServer][Info   ] Version done in 00:00:00.
[20:59:33.129][Updater        ][Info   ] Checking for updates on channel beta…
[20:59:33.134][Notifications  ][Info   ] Docker is starting…
[20:59:33.149][NamedPipeClient][Info   ] Sending Start(Docker.Core.Settings)…
[20:59:33.154][NamedPipeServer][Info   ] Start(Docker.Core.Settings)
[20:59:33.159][PowerMode      ][Info   ] Stop
[20:59:33.185][Updater        ][Info   ] Local build 10300 is as good as the remote 10300 on channel beta
[20:59:33.164][HyperV         ][Info   ] Stop
[20:59:33.179][PowerShell     ][Info   ] Run script with parameters: -Stop True…
[20:59:33.179][PowerShell     ][Info   ] Creating a Runspace Pool…
[20:59:33.418][PowerShell     ][Info   ] Runspace Pool created (Min=1, Max=2)
[20:59:33.528][HyperV         ][Info   ] Script started at 20:59:33.519
[20:59:36.053][HyperV         ][Info   ] Module loaded at 20:59:36.052
[20:59:36.273][HyperV         ][Info   ] VM MobyLinuxVM does not exist
[20:59:36.273][HyperV         ][Debug  ] [stop] took 00:00:03.1091144 to run
[20:59:36.274][OptimizeDisk   ][Info   ] Optimize
[20:59:36.275][PowerShell     ][Info   ] Run script…
[20:59:36.301][Moby           ][Info   ] Stop
[20:59:36.313][HyperVGuids    ][Info   ] Installing GUIDs…
[20:59:36.314][PowerMode      ][Info   ] Start
[20:59:36.314][HyperV         ][Info   ] Create
[20:59:36.315][PowerShell     ][Info   ] Run script with parameters: -Create True -VhdPathOverride  -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso…
[20:59:36.315][HyperVGuids    ][Info   ] GUIDs installed
[20:59:36.319][Firewall       ][Info   ] Removing all existing rules…
[20:59:36.327][HyperV         ][Info   ] Script started at 20:59:36.327
[20:59:36.347][HyperV         ][Info   ] Module loaded at 20:59:36.346
[20:59:36.354][Firewall       ][Info   ] All existing rules are removed.
[20:59:36.355][Firewall       ][Info   ] Opening ports for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe…
[20:59:36.364][Firewall       ][Info   ] Opening ports for SMB…
[20:59:36.407][Firewall       ][Info   ] Ports are opened
[20:59:36.601][HyperV         ][Info   ] Creating Switch: DockerNAT…
[20:59:38.429][HyperV         ][Info   ] Switch created.
[20:59:39.252][HyperV         ][Info   ] Set IP address on switch
[20:59:40.599][HyperV         ][Info   ] Creating VM MobyLinuxVM…
[20:59:42.107][HyperV         ][Info   ] Setting CPUs to 2 and Memory to 2048 MB
[20:59:42.456][HyperV         ][Info   ] Attach VHD C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\MobyLinuxVM.vhdx
[20:59:43.450][HyperV         ][Info   ] Connect Internal Switch DockerNAT
[20:59:44.071][HyperV         ][Info   ] Attach DVD C:\Program Files\Docker\Docker\Resources\mobylinux.iso
[20:59:44.941][HyperV         ][Info   ] Disabled Guest Service Interface
[20:59:44.975][HyperV         ][Info   ] Enabled Heartbeat
[20:59:45.016][HyperV         ][Info   ] Disabled Key-Value Pair Exchange
[20:59:45.051][HyperV         ][Info   ] Enabled Shutdown
[20:59:45.075][HyperV         ][Info   ] Enabled Time Synchronization
[20:59:45.102][HyperV         ][Info   ] Disabled VSS
[20:59:45.586][HyperV         ][Info   ] VM created.
[20:59:45.586][HyperV         ][Debug  ] [create] took 00:00:09.2717871 to run
[20:59:45.586][PowerShell     ][Info   ] Run script ‘(Get-VM MobyLinuxVM).Id.Guid’…
[20:59:45.664][DataKit        ][Info   ] Starting C:\Program Files\Docker\Docker\Resources\com.docker.db.exe –url hyperv-connect://759575fe-c030-478c-b5b5-07dc2bfbdae0,\\.\pipe\dockerDataBase –color never
[20:59:45.684][DataKit        ][Info   ] Started
[20:59:45.713][Database       ][Info   ] Generating CA Cert Bundle
[20:59:45.756][Database       ][Info   ] CA Cert Bundle Generated
[20:59:45.757][DataKit        ][Info   ] Starting com.docker.db.exe 0.7.0-34-g6f04213 …
[20:59:45.782][DataKit        ][Info   ] com.docker.db.exe: accepted a new connection on \\.\pipe\dockerDataBase
[20:59:45.785][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/config=static
[20:59:45.785][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/address=10.0.75.2
[20:59:45.785][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/netmask=255.255.255.0
[20:59:45.785][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/gateway=10.0.75.1
[20:59:45.785][Database       ][Info   ] Writing com.docker.driver.amd64-linux/network=hybrid
[20:59:45.785][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/docker/daemon.json={“registry-mirrors”:[],”insecure-registries”:[]}
[20:59:45.785][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/sysctl.conf=
[20:59:45.785][Database       ][Info   ] Writing com.docker.driver.amd64-linux/native/port-forwarding=true
[20:59:45.840][DataKit        ][Info   ] com.docker.db.exe: accepted a new connection on \\.\pipe\dockerDataBase
[20:59:45.841][DataKit        ][Info   ] com.docker.db.exe: Using protocol TwoThousand msize 16384
[20:59:46.252][Database       ][Info   ] Successfully wrote 8 value(s)
[20:59:46.257][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/ssl/certs/ca-certificates.crt=C:\WINDOWS\TEMP\tmp7396.tmp
[20:59:46.298][DataKit        ][Info   ] com.docker.db.exe: accepted a new connection on \\.\pipe\dockerDataBase
[20:59:46.298][DataKit        ][Info   ] com.docker.db.exe: Using protocol TwoThousand msize 16384
[20:59:46.412][Database       ][Info   ] Successfully wrote value
[20:59:46.422][Moby           ][Info   ] Connecting…
[20:59:46.422][Moby           ][Error  ] Failed to read Moby’s logs: The operation has timed out.
[20:59:46.427][HyperV         ][Info   ] Start
[20:59:46.427][PowerShell     ][Info   ] Run script with parameters: -Start True…
[20:59:46.446][PowerShell     ][Info   ] Run script ‘$(Find-NetRoute -RemoteIPAddress 8.8.8.8).InterfaceIndex[0]’…
[20:59:46.446][HyperV         ][Info   ] Script started at 20:59:46.446
[20:59:46.502][HyperV         ][Info   ] Module loaded at 20:59:46.487
[20:59:46.512][HyperV         ][Info   ] Starting VM MobyLinuxVM…
[20:59:47.042][HyperV         ][Debug  ] [start] took 00:00:00.6154955 to run
[20:59:47.227][Database       ][Info   ] Writing com.docker.driver.amd64-linux/slirp/dns=nameserver 192.168.2.254

[20:59:47.266][DataKit        ][Info   ] com.docker.db.exe: accepted a new connection on \\.\pipe\dockerDataBase
[20:59:47.266][DataKit        ][Info   ] com.docker.db.exe: Using protocol TwoThousand msize 16384
[20:59:47.376][Database       ][Info   ] Successfully wrote 1 value(s)
[20:59:47.451][VpnKit         ][Info   ] Starting C:\Program Files\Docker\Docker\Resources\com.docker.slirp.exe –ethernet hyperv-connect://759575fe-c030-478c-b5b5-07dc2bfbdae0 –port hyperv-connect://759575fe-c030-478c-b5b5-07dc2bfbdae0 –db \\.\pipe\dockerDataBase –debug –diagnostics \\.\pipe\dockerVpnKitDiagnostics
[20:59:47.456][VpnKit         ][Info   ] Started
[20:59:47.456][Linux          ][Info   ] Trying to connect to vsud…
[20:59:47.517][VpnKit         ][Info   ] com.docker.slirp.exe: Logging to stdout (stdout:true DEBUG:false)
[20:59:47.517][VpnKit         ][Info   ] com.docker.slirp.exe: Setting handler to ignore all SIGPIPE signals
[20:59:47.517][VpnKit         ][Info   ] com.docker.slirp.exe: vpnkit version c41f7c8589352c95b14de636c895e8fbd72222e5 with hostnet version   uwt version 0.0.3 hvsock version 0.13.0
[20:59:47.517][VpnKit         ][Info   ] com.docker.slirp.exe: starting port forwarding server on port_control_url:hyperv-connect://759575fe-c030-478c-b5b5-07dc2bfbda vsock_path:
[20:59:47.517][VpnKit         ][Info   ] com.docker.slirp.exe: connecting to 759575fe-c030-478c-b5b5-07dc2bfbdae0:0B95756A-9985-48AD-9
[20:59:47.522][VpnKit         ][Info   ] com.docker.slirp.exe: connecting to 759575fe-c030-478c-b5b5-07dc2bfbdae0:30D48B34-7D27-4B0B
[20:59:47.522][VpnKit         ][Error  ] com.docker.slirp.exe: While watching /etc/resolv.conf: ENOENT
[20:59:47.522][VpnKit         ][Info   ] com.docker.slirp.exe: hosts file has bindings for
[20:59:48.433][Moby           ][Info   ] Connected
[20:59:48.904][Moby           ][Info   ] Performing relocations… done.
[20:59:48.909][Moby           ][Info   ] Booting the kernel.
[20:59:48.919][Moby           ][Info   ] Linux version 4.9.12-moby (root@11fbdc1f630f) (gcc version 6.2.1 20160822 (Alpine 6.2.1) ) #1 SMP Tue Feb 28 12:11:36 UTC 2017
[20:59:48.929][Moby           ][Info   ] Command line: earlyprintk=ttyS0,115200 console=ttyS0,115200 mobyplatform=windows vsyscall=emulate panic=1 rootdelay=300 noautodetect
[20:59:48.929][Moby           ][Info   ]
[20:59:48.939][Moby           ][Info   ] x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
[20:59:48.947][Moby           ][Info   ] x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
[20:59:48.952][Moby           ][Info   ] x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
[20:59:48.952][Moby           ][Info   ] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[20:59:48.957][Moby           ][Info   ] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using ‘standard’ format.
[20:59:48.962][Moby           ][Info   ] x86/fpu: Using ‘eager’ FPU context switches.
[20:59:48.967][Moby           ][Info   ] e820: BIOS-provided physical RAM map:
[20:59:48.977][Moby           ][Info   ] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[20:59:48.982][Moby           ][Info   ] BIOS-e820: [mem 0x0000000000100000-0x000000007eeedfff] usable
[20:59:48.988][Moby           ][Info   ] BIOS-e820: [mem 0x000000007eeee000-0x000000007eef1fff] ACPI data
[20:59:48.993][Moby           ][Info   ] BIOS-e820: [mem 0x000000007eef2000-0x000000007ef1afff] reserved
[20:59:48.998][Moby           ][Info   ] BIOS-e820: [mem 0x000000007ef1b000-0x000000007ff9afff] usable
[20:59:48.999][Moby           ][Info   ] BIOS-e820: [mem 0x000000007ff9b000-0x000000007fff2fff] reserved
[20:59:49.004][Moby           ][Info   ] BIOS-e820: [mem 0x000000007fff3000-0x000000007fffafff] ACPI data
[20:59:49.009][Moby           ][Info   ] BIOS-e820: [mem 0x000000007fffb000-0x000000007fffefff] ACPI NVS
[20:59:49.014][Moby           ][Info   ] BIOS-e820: [mem 0x000000007ffff000-0x000000007fffffff] usable
[20:59:49.019][Moby           ][Info   ] bootconsole [earlyser0] enabled
[20:59:49.024][Moby           ][Info   ] NX (Execute Disable) protection: active
[20:59:49.029][Moby           ][Info   ] efi: EFI v2.31 by EDK II
[20:59:49.039][Moby           ][Info   ] efi:  ACPI=0x7fffa000  ACPI 2.0=0x7fffa014  SMBIOS=0x7fff2000  PROP=0x419a3d8  MEMATTR=0x7f51cd18
[20:59:49.044][Moby           ][Info   ] SMBIOS 2.4 present.
[20:59:49.044][Moby           ][Info   ] Hypervisor detected: Microsoft HyperV
[20:59:49.048][Moby           ][Info   ] HyperV: features 0x2e7f, hints 0x2c2c
[20:59:49.058][Moby           ][Info   ] HyperV: LAPIC Timer Frequency: 0x1e8480
[20:59:49.063][Moby           ][Info   ] clocksource: hyperv_clocksource: mask: 0xffffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns: 440795202120 ns
[20:59:49.068][Moby           ][Info   ] tsc: Marking TSC unstable due to running on Hyper-V
[20:59:49.073][Moby           ][Info   ] e820: last_pfn = 0x80000 max_arch_pfn = 0x400000000
[20:59:49.078][Moby           ][Info   ] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT
[20:59:49.083][Moby           ][Info   ] Memory KASLR using RDRAND RDTSC…
[20:59:49.089][Moby           ][Info   ] Using GB pages for direct mapping
[20:59:49.094][Moby           ][Info   ] RAMDISK: [mem 0x77ce6000-0x7b299fff]
[20:59:49.098][Moby           ][Info   ] ACPI: Early table checksum verification disabled
[20:59:49.100][Moby           ][Info   ] ACPI: RSDP 0x000000007FFFA014 000024 (v02 VRTUAL)
[20:59:49.105][Moby           ][Info   ] ACPI: XSDT 0x000000007FFF90E8 00005C (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[20:59:49.115][Moby           ][Info   ] ACPI: FACP 0x000000007FFF7000 0000F4 (v04 VRTUAL MICROSFT 00000001 MSFT 00000001)
[20:59:49.120][Moby           ][Info   ] ACPI: DSDT 0x000000007EEEF000 00256F (v02 MSFTVM DSDT01   00000001 MSFT 04000000)
[20:59:49.125][Moby           ][Info   ] ACPI: FACS 0x000000007FFFE000 000040
[20:59:49.130][Moby           ][Info   ] ACPI: APIC 0x000000007FFF8000 0007D2 (v02 VRTUAL MICROSFT 00000001 MSFT 00000001)
[20:59:49.140][Moby           ][Info   ] ACPI: OEM0 0x000000007FFF6000 000064 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[20:59:49.146][Moby           ][Info   ] ACPI: WAET 0x000000007FFF5000 000028 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[20:59:49.153][Moby           ][Info   ] ACPI: OEM1 0x000000007FFF4000 00009E (v02 MSFTVM UARTS    00000001 MSFT 04000000)
[20:59:49.158][Moby           ][Info   ] ACPI: OEM2 0x000000007FFF3000 0002E2 (v02 MSFTVM VTPM2    00000001 MSFT 04000000)
[20:59:49.163][Moby           ][Info   ] ACPI: SRAT 0x000000007EEEE000 000190 (v02 VRTUAL MICROSFT 00000001 MSFT 00000001)
[20:59:49.183][Moby           ][Info   ] Zone ranges:
[20:59:49.193][Moby           ][Info   ]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[20:59:49.200][Moby           ][Info   ]   DMA32    [mem 0x0000000001000000-0x000000007fffffff]
[20:59:49.205][Moby           ][Info   ]   Normal   empty
[20:59:49.210][Moby           ][Info   ] Movable zone start for each node
[20:59:49.215][Moby           ][Info   ] Early memory node ranges
[20:59:49.215][Moby           ][Info   ]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[20:59:49.220][Moby           ][Info   ]   node   0: [mem 0x0000000000100000-0x000000007eeedfff]
[20:59:49.225][Moby           ][Info   ]   node   0: [mem 0x000000007ef1b000-0x000000007ff9afff]
[20:59:49.230][Moby           ][Info   ]   node   0: [mem 0x000000007ffff000-0x000000007fffffff]
[20:59:49.235][Moby           ][Info   ] Initmem setup node 0 [mem 0x0000000000001000-0x000000007fffffff]
[20:59:49.246][Moby           ][Info   ] ACPI: PM-Timer IO Port: 0x408
[20:59:49.248][Moby           ][Info   ] ————[ cut here ]————
[20:59:49.258][Moby           ][Info   ] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:2065 __generic_processor_info+0x149/0x24f
[20:59:49.263][Moby           ][Info   ] Only 127 processors supported.Processor 128/0x80 and the rest are ignored.
[20:59:49.268][Moby           ][Info   ] Modules linked in:
[20:59:49.273][Moby           ][Info   ] CPU: 0 PID: 0 Comm: swapper Not tainted 4.9.12-moby #1
[20:59:49.278][Moby           ][Info   ] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v1.0 11/26/2012
[20:59:49.283][Moby           ][Info   ]  0000000000000000 ffffffffbd41a0d3 ffffffffbde03d40 0000000000000000
[20:59:49.293][Moby           ][Info   ]  ffffffffbd0dcd80 0000000000000080 ffffffffbde03da0 0000000000000000
[20:59:49.299][Moby           ][Info   ]  0000000000000014 0000000000000000 0000000000000000 ffffffffbd0dcdf3
[20:59:49.300][Moby           ][Info   ] Call Trace:
[20:59:49.305][Moby           ][Info   ]  [<ffffffffbd41a0d3>] ? dump_stack+0x5a/0x6f
[20:59:49.310][Moby           ][Info   ]  [<ffffffffbd0dcd80>] ? __warn+0xd2/0xeb
[20:59:49.315][Moby           ][Info   ]  [<ffffffffbd0dcdf3>] ? warn_slowpath_fmt+0x5a/0x76
[20:59:49.320][Moby           ][Info   ]  [<ffffffffbdfa6e6e>] ? __early_ioremap+0x13d/0x1bd
[20:59:49.325][Moby           ][Info   ]  [<ffffffffbd03802e>] ? __generic_processor_info+0x149/0x24f
[20:59:49.330][Moby           ][Info   ]  [<ffffffffbd034539>] ? acpi_register_lapic+0x46/0x72
[20:59:49.335][Moby           ][Info   ]  [<ffffffffbdf8d2f1>] ? acpi_parse_lapic+0x3f/0x44
[20:59:49.340][Moby           ][Info   ]  [<ffffffffbdfb7a0f>] ? acpi_parse_entries_array+0xef/0x145
[20:59:49.349][Moby           ][Info   ]  [<ffffffffbdfb7bcb>] ? acpi_table_parse_entries_array+0xbe/0xf7
[20:59:49.354][Moby           ][Info   ]  [<ffffffffbdf8dcca>] ? acpi_boot_init+0xed/0x45e
[20:59:49.359][Moby           ][Info   ]  [<ffffffffbd04254c>] ? pmd_val+0x7/0x8
[20:59:49.364][Moby           ][Info   ]  [<ffffffffbd0425c5>] ? pmd_page_vaddr+0x9/0x30
[20:59:49.364][Moby           ][Info   ]  [<ffffffffbdf8d2b2>] ? acpi_parse_x2apic_nmi+0x3c/0x3c
[20:59:49.369][Moby           ][Info   ]  [<ffffffffbdf8d713>] ? dmi_ignore_irq0_timer_override+0x26/0x26
[20:59:49.374][Moby           ][Info   ]  [<ffffffffbdf87472>] ? setup_arch+0x889/0x984
[20:59:49.385][Moby           ][Info   ]  [<ffffffffbdf7cb85>] ? start_kernel+0xa9/0x44a
[20:59:49.389][Moby           ][Info   ]  [<ffffffffbdf7c120>] ? early_idt_handler_array+0x120/0x120
[20:59:49.393][Moby           ][Info   ]  [<ffffffffbdf7c3fd>] ? x86_64_start_kernel+0x141/0x165
[20:59:49.398][Moby           ][Info   ] —[ end trace 7c093e9440561719 ]—
[20:59:49.400][Moby           ][Info   ] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[20:59:49.415][Moby           ][Info   ] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
[20:59:49.420][Moby           ][Info   ] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[20:59:49.425][Moby           ][Info   ] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[20:59:49.425][Moby           ][Info   ] Using ACPI (MADT) for SMP configuration information
[20:59:49.430][Moby           ][Info   ] smpboot: 240 Processors exceeds NR_CPUS limit of 128
[20:59:49.440][Moby           ][Info   ] smpboot: Allowing 128 CPUs, 126 hotplug CPUs
[20:59:49.449][Moby           ][Info   ] e820: [mem 0x80000000-0xffffffff] available for PCI devices
[20:59:49.459][Moby           ][Info   ] Booting paravirtualized kernel on bare hardware
[20:59:49.479][Moby           ][Info   ] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[20:59:49.492][Moby           ][Info   ] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:128 nr_node_ids:1
[20:59:49.525][Moby           ][Info   ] percpu: Embedded 35 pages/cpu @ffff9d6475c00000 s105048 r8192 d30120 u262144
[20:59:49.546][Moby           ][Info   ] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 515799
[20:59:49.560][Moby           ][Info   ] Kernel command line: earlyprintk=ttyS0,115200 console=ttyS0,115200 mobyplatform=windows vsyscall=emulate panic=1 rootdelay=300 noautodetect
[20:59:49.560][Moby           ][Info   ]
[20:59:49.571][Moby           ][Info   ] log_buf_len individual max cpu contribution: 4096 bytes
[20:59:49.587][Moby           ][Info   ] log_buf_len total cpu_extra contributions: 520192 bytes
[20:59:49.615][Moby           ][Info   ] log_buf_len min size: 131072 bytes
[20:59:49.630][Moby           ][Info   ] log_buf_len: 1048576 bytes
[20:59:49.642][Moby           ][Info   ] early log buf free: 120596(92%)
[20:59:49.647][Moby           ][Info   ] PID hash table entries: 4096 (order: 3, 32768 bytes)
[20:59:49.667][Moby           ][Info   ] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[20:59:49.697][Moby           ][Info   ] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[20:59:49.749][Moby           ][Info   ] Memory: 1953204K/2096184K available (8496K kernel code, 1410K rwdata, 2860K rodata, 1392K init, 600K bss, 142980K reserved, 0K cma-reserved)
[20:59:49.777][Moby           ][Info   ] Hierarchical RCU implementation.
[20:59:49.794][Moby           ][Info   ]  Build-time adjustment of leaf fanout to 64.
[20:59:49.820][Moby           ][Info   ] Using NULL legacy PIC
[20:59:49.825][Moby           ][Info   ] NR_IRQS:8448 nr_irqs:1448 0
[20:59:49.861][Moby           ][Info   ] Console: colour dummy device 80×25
[20:59:49.876][Moby           ][Info   ] console [ttyS0] enabled
[20:59:49.898][Moby           ][Info   ] console [ttyS0] enabled
[20:59:49.915][Moby           ][Info   ] bootconsole [earlyser0] disabled
[20:59:49.920][Moby           ][Info   ] bootconsole [earlyser0] disabled
[20:59:49.979][Moby           ][Info   ] tsc: Fast TSC calibration failed
[20:59:49.988][Moby           ][Info   ] tsc: Unable to calibrate against PIT
[20:59:49.993][Moby           ][Info   ] tsc: using PMTIMER reference calibration
[20:59:49.998][Moby           ][Info   ] tsc: Detected 2312.707 MHz processor
[20:59:50.005][Moby           ][Info   ] Calibrating delay loop (skipped), value calculated using timer frequency.. 4625.41 BogoMIPS (lpj=23127070)
[20:59:50.010][Moby           ][Info   ] pid_max: default: 131072 minimum: 1024
[20:59:50.015][Moby           ][Info   ] ACPI: Core revision 20160831
[20:59:50.020][Moby           ][Info   ] ACPI: 1 ACPI AML tables successfully acquired and loaded
[20:59:50.030][Moby           ][Info   ] Security Framework initialized
[20:59:50.035][Moby           ][Info   ] Yama: becoming mindful.
[20:59:50.040][Moby           ][Info   ] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[20:59:50.049][Moby           ][Info   ] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[20:59:50.054][Moby           ][Info   ] CPU: Physical Processor ID: 0
[20:59:50.059][Moby           ][Info   ] CPU: Processor Core ID: 0
[20:59:50.070][Moby           ][Info   ] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
[20:59:50.074][Moby           ][Info   ] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
[20:59:50.084][Moby           ][Info   ] Freeing SMP alternatives memory: 24K (ffffffffbe0be000 – ffffffffbe0c4000)
[20:59:50.100][Moby           ][Info   ] ftrace: allocating 37627 entries in 147 pages
[20:59:50.156][Moby           ][Info   ] smpboot: Max logical packages: 120
[20:59:50.182][Moby           ][Info   ] Switched APIC routing to physical flat.
[20:59:50.235][Moby           ][Info   ] smpboot: CPU0: Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz (family: 0x6, model: 0x45, stepping: 0x1)
[20:59:50.310][Moby           ][Info   ] Performance Events: unsupported p6 CPU model 69 no PMU driver, software events only.
[20:59:50.466][Moby           ][Info   ] NMI watchdog: disabled (cpu0): hardware events not enabled
[20:59:50.495][Moby           ][Info   ] NMI watchdog: Shutting down hard lockup detector on all cpus
[20:59:50.511][Moby           ][Info   ] x86: Booting SMP configuration:
[20:59:50.726][Moby           ][Info   ] …. node  #0, CPUs:          #1calibrate_delay_direct() dropping max bogoMips estimate 4 = 27829749
[20:59:50.741][Moby           ][Info   ] x86: Booted up 1 node, 2 CPUs
[20:59:50.769][Moby           ][Info   ] smpboot: Total of 2 processors activated (9249.95 BogoMIPS)
[20:59:50.784][Moby           ][Info   ] devtmpfs: initialized
[20:59:50.810][Moby           ][Info   ] x86/mm: Memory block size: 128MB
[20:59:50.869][Moby           ][Info   ] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[20:59:50.921][Moby           ][Info   ] futex hash table entries: 32768 (order: 9, 2097152 bytes)
[20:59:50.970][Moby           ][Info   ] NET: Registered protocol family 16
[20:59:51.036][Moby           ][Info   ] cpuidle: using governor ladder
[20:59:51.080][Moby           ][Info   ] cpuidle: using governor menu
[20:59:51.106][Moby           ][Info   ] ACPI: bus type PCI registered
[20:59:51.126][Moby           ][Info   ] PCI: Fatal: No config space access function found
[20:59:51.185][Moby           ][Info   ] HugeTLB registered 1 GB page size, pre-allocated 0 pages
[20:59:51.201][Moby           ][Info   ] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[20:59:51.221][Moby           ][Info   ] ACPI: Added _OSI(Module Device)
[20:59:51.301][Moby           ][Info   ] ACPI: Added _OSI(Processor Device)
[20:59:51.366][Moby           ][Info   ] ACPI: Added _OSI(3.0 _SCP Extensions)
[20:59:51.430][Moby           ][Info   ] ACPI: Added _OSI(Processor Aggregator Device)
[20:59:51.616][Moby           ][Info   ] ACPI: Executed 1 blocks of module-level executable AML code
[20:59:51.673][Moby           ][Info   ] ACPI: Dynamic OEM Table Load:
[20:59:51.714][Moby           ][Info   ] ACPI: Interpreter enabled
[20:59:51.745][Moby           ][Info   ] ACPI: (supports S0 S5)
[20:59:51.768][Moby           ][Info   ] ACPI: Using IOAPIC for interrupt routing
[20:59:51.814][Moby           ][Info   ] PCI: Using host bridge windows from ACPI; if necessary, use “pci=nocrs” and report a bug
[20:59:51.859][Moby           ][Info   ] ACPI: Enabled 1 GPEs in block 00 to 0F
[20:59:51.876][Moby           ][Info   ] SCSI subsystem initialized
[20:59:51.902][Moby           ][Info   ] pps_core: LinuxPPS API ver. 1 registered
[20:59:51.929][Moby           ][Info   ] pps_core: Software ver. 5.3.6 – Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[20:59:51.939][Moby           ][Info   ] PTP clock support registered
[20:59:51.949][Moby           ][Info   ] Registered efivars operations
[20:59:51.965][Moby           ][Info   ] wmi: Mapper loaded
[20:59:52.025][Moby           ][Info   ] clocksource: hyperv_clocksource_tsc_page: mask: 0xffffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns: 440795202120 ns
[20:59:52.050][Moby           ][Info   ] hv_vmbus: Hyper-V Host Build:14393-10.0-0-0.576; Vmbus version:4.0
[20:59:52.079][Moby           ][Info   ] PCI: Using ACPI for IRQ routing
[20:59:52.095][Moby           ][Info   ] PCI: System does not support PCI
[20:59:52.110][Moby           ][Info   ] NetLabel: Initializing
[20:59:52.145][Moby           ][Info   ] NetLabel:  domain hash size = 128
[20:59:52.188][Moby           ][Info   ] NetLabel:  protocols = UNLABELED CIPSOv4
[20:59:52.236][Moby           ][Info   ] NetLabel:  unlabeled traffic allowed by default
[20:59:52.366][Moby           ][Info   ] clocksource: Switched to clocksource hyperv_clocksource_tsc_page
[20:59:52.427][Moby           ][Info   ] FS-Cache: Loaded
[20:59:52.571][Moby           ][Info   ] CacheFiles: Loaded
[20:59:52.687][Moby           ][Info   ] pnp: PnP ACPI init
[20:59:52.832][Moby           ][Info   ] pnp: PnP ACPI: found 3 devices
[20:59:52.906][Moby           ][Info   ] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[20:59:52.971][Moby           ][Info   ] NET: Registered protocol family 2
[20:59:53.054][Moby           ][Info   ] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[20:59:53.091][Moby           ][Info   ] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[20:59:53.128][Moby           ][Info   ] TCP: Hash tables configured (established 16384 bind 16384)
[20:59:53.168][Moby           ][Info   ] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[20:59:53.239][Moby           ][Info   ] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[20:59:53.286][Moby           ][Info   ] NET: Registered protocol family 1
[20:59:53.354][Moby           ][Info   ] RPC: Registered named UNIX socket transport module.
[20:59:53.413][Moby           ][Info   ] RPC: Registered udp transport module.
[20:59:53.563][Moby           ][Info   ] RPC: Registered tcp transport module.
[20:59:53.891][Moby           ][Info   ] RPC: Registered tcp NFSv4.1 backchannel transport module.
[20:59:53.921][Moby           ][Info   ] Unpacking initramfs…
[20:59:54.956][Moby           ][Info   ] random: fast init done
[20:59:55.740][Moby           ][Info   ] Freeing initrd memory: 54992K (ffff9d6477ce6000 – ffff9d647b29a000)
[20:59:55.816][Moby           ][Info   ] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 10737418240 ms ovfl timer
[20:59:55.845][Moby           ][Info   ] RAPL PMU: hw unit of domain pp0-core 2^-0 Joules
[20:59:55.875][Moby           ][Info   ] RAPL PMU: hw unit of domain package 2^-0 Joules
[20:59:55.915][Moby           ][Info   ] RAPL PMU: hw unit of domain dram 2^-0 Joules
[20:59:55.935][Moby           ][Info   ] RAPL PMU: hw unit of domain pp1-gpu 2^-0 Joules
[20:59:55.980][Moby           ][Info   ] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2156191e7dd, max_idle_ns: 440795316529 ns
[20:59:56.016][Moby           ][Info   ] audit: initializing netlink subsys (disabled)
[20:59:56.041][Moby           ][Info   ] audit: type=2000 audit(1488488392.630:1): initialized
[20:59:56.071][Moby           ][Info   ] workingset: timestamp_bits=46 max_order=19 bucket_order=0
[20:59:56.096][Moby           ][Info   ] FS-Cache: Netfs ‘nfs’ registered for caching
[20:59:56.119][Moby           ][Info   ] NFS: Registering the id_resolver key type
[20:59:56.139][Moby           ][Info   ] Key type id_resolver registered
[20:59:56.159][Moby           ][Info   ] Key type id_legacy registered
[20:59:56.176][Moby           ][Info   ] nfs4filelayout_init: NFSv4 File Layout Driver Registering…
[20:59:56.209][Moby           ][Info   ] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[20:59:56.229][Moby           ][Info   ] FS-Cache: Netfs ‘cifs’ registered for caching
[20:59:56.244][Moby           ][Info   ] ntfs: driver 2.1.32 [Flags: R/O].
[20:59:56.270][Moby           ][Info   ] fuse init (API version 7.26)
[20:59:56.296][Moby           ][Info   ] 9p: Installing v9fs 9p2000 file system support
[20:59:56.319][Moby           ][Info   ] FS-Cache: Netfs ‘9p’ registered for caching
[20:59:56.334][Moby           ][Info   ] aufs 4.9-20170220
[20:59:56.359][Moby           ][Info   ] NET: Registered protocol family 38
[20:59:56.381][Moby           ][Info   ] Key type asymmetric registered
[20:59:56.396][Moby           ][Info   ] Asymmetric key parser ‘x509’ registered
[20:59:56.454][Moby           ][Info   ] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[20:59:56.481][Moby           ][Info   ] io scheduler noop registered
[20:59:56.514][Moby           ][Info   ] io scheduler deadline registered (default)
[20:59:56.539][Moby           ][Info   ] io scheduler cfq registered
[20:59:56.597][Moby           ][Info   ] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[20:59:56.629][Moby           ][Info   ] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[20:59:56.659][Moby           ][Info   ] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[20:59:56.692][Moby           ][Info   ] hv_vmbus: registering driver hyperv_fb
[20:59:56.710][Moby           ][Info   ] GHES: HEST is not enabled!
[20:59:56.730][Moby           ][Info   ] xenfs: not registering filesystem on non-xen platform
[20:59:56.766][Moby           ][Info   ] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[20:59:56.947][Moby           ][Info   ] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[20:59:57.077][Moby           ][Info   ] 00:02: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[20:59:57.092][Moby           ][Info   ] Initializing Nozomi driver 2.1d
[20:59:57.114][Moby           ][Info   ] Non-volatile memory driver v1.3
[20:59:57.154][Moby           ][Info   ] Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds, margin is 60 seconds).
[20:59:57.177][Moby           ][Info   ] loop: module loaded
[20:59:57.202][Moby           ][Info   ] nbd: registered device at major 43
[20:59:57.219][Moby           ][Info   ] VMware PVSCSI driver – version 1.0.7.0-k
[20:59:57.234][Moby           ][Info   ] hv_vmbus: registering driver hv_storvsc
[20:59:57.254][Moby           ][Info   ] scsi host0: storvsc_host_t
[20:59:57.308][Moby           ][Info   ] scsi 0:0:0:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[20:59:57.384][Moby           ][Info   ] scsi 0:0:0:1: CD-ROM            Msft     Virtual DVD-ROM  1.0  PQ: 0 ANSI: 0
[20:59:57.465][Moby           ][Info   ] sd 0:0:0:0: [sda] 125829120 512-byte logical blocks: (64.4 GB/60.0 GiB)
[20:59:57.549][Moby           ][Info   ] sr 0:0:0:1: [sr0] scsi3-mmc drive: 0x/0x caddy
[20:59:57.674][Moby           ][Info   ] cdrom: Uniform CD-ROM driver Revision: 3.20
[20:59:57.728][Moby           ][Info   ] sd 0:0:0:0: Attached scsi generic sg0 type 0
[20:59:57.750][Moby           ][Info   ] sr 0:0:0:1: Attached scsi generic sg1 type 5
[20:59:57.779][Moby           ][Info   ] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[20:59:57.813][Moby           ][Info   ] tun: Universal TUN/TAP device driver, 1.6
[20:59:57.863][Moby           ][Info   ] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[20:59:57.899][Moby           ][Info   ] e1000: Intel(R) PRO/1000 Network Driver – version 7.3.21-k8-NAPI
[20:59:57.923][Moby           ][Info   ] e1000: Copyright (c) 1999-2006 Intel Corporation.
[20:59:57.958][Moby           ][Info   ] e1000e: Intel(R) PRO/1000 Network Driver – 3.2.6-k
[20:59:58.003][Moby           ][Info   ] e1000e: Copyright(c) 1999 – 2015 Intel Corporation.
[20:59:58.038][Moby           ][Info   ] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver – version 3.2.2-k
[20:59:58.086][Moby           ][Info   ] ixgbevf: Copyright (c) 2009 – 2015 Intel Corporation.
[20:59:58.131][Moby           ][Info   ] PPP generic driver version 2.4.2
[20:59:58.157][Moby           ][Info   ] PPP BSD Compression module registered
[20:59:58.176][Moby           ][Info   ] PPP Deflate Compression module registered
[20:59:58.196][Moby           ][Info   ] PPP MPPE Compression module registered
[20:59:58.216][Moby           ][Info   ] NET: Registered protocol family 24
[20:59:58.231][Moby           ][Info   ] PPTP driver version 0.8.5
[20:59:58.256][Moby           ][Info   ] VMware vmxnet3 virtual NIC driver – version 1.4.a.0-k-NAPI
[20:59:58.291][Moby           ][Info   ] hv_vmbus: registering driver hv_netvsc
[20:59:58.316][Moby           ][Info   ] sd 0:0:0:0: [sda] 4096-byte physical blocks
[20:59:58.351][Moby           ][Info   ] sd 0:0:0:0: [sda] Write Protect is off
[20:59:58.392][Moby           ][Info   ] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[20:59:58.412][Moby           ][Info   ]  sda: sda1
[20:59:58.432][Moby           ][Info   ] sd 0:0:0:0: [sda] Attached SCSI disk
[20:59:58.501][Moby           ][Info   ] hv_netvsc: hv_netvsc channel opened successfully
[20:59:58.568][Moby           ][Info   ] hv_netvsc 9bc43e21-df89-4ce2-a132-ccd51ba90a18: Send section size: 6144, Section count:2560
[20:59:58.622][Moby           ][Info   ] hv_netvsc 9bc43e21-df89-4ce2-a132-ccd51ba90a18: Device MAC 00:15:5d:3a:31:27 link state up
[20:59:58.662][Moby           ][Info   ] Fusion MPT base driver 3.04.20
[20:59:58.708][Moby           ][Info   ] Copyright (c) 1999-2008 LSI Corporation
[20:59:58.728][Moby           ][Info   ] Fusion MPT SPI Host driver 3.04.20
[20:59:58.747][Moby           ][Info   ] aoe: AoE v85 initialised.
[20:59:58.778][Moby           ][Info   ] i8042: PNP: No PS/2 controller found. Probing ports directly.
[21:00:00.196][Moby           ][Info   ] i8042: No controller found
[21:00:00.216][Moby           ][Info   ] hv_vmbus: registering driver hyperv_keyboard
[21:00:00.296][Moby           ][Info   ] mousedev: PS/2 mouse device common for all mice
[21:00:00.346][Moby           ][Info   ] input: PC Speaker as /devices/platform/pcspkr/input/input0
[21:00:00.362][Moby           ][Info   ] rtc_cmos 00:00: RTC can wake from S4
[21:00:00.436][Moby           ][Info   ] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
[21:00:00.467][Moby           ][Info   ] rtc_cmos 00:00: alarms up to one month, 114 bytes nvram
[21:00:00.480][Moby           ][Info   ] i2c /dev entries driver
[21:00:00.496][Moby           ][Info   ] EFI Variables Facility v0.08 2004-May-17
[21:00:00.521][Moby           ][Info   ] pstore: using zlib compression
[21:00:00.555][Moby           ][Info   ] pstore: Registered efi as persistent store backend
[21:00:00.662][Moby           ][Info   ] hv_utils: Registering HyperV Utility Driver
[21:00:00.746][Moby           ][Info   ] hv_vmbus: registering driver hv_util
[21:00:00.806][Moby           ][Info   ] hv_utils: Heartbeat IC version 3.0
[21:00:00.821][Moby           ][Info   ] hv_utils: Shutdown IC version 3.0
[21:00:00.846][Moby           ][Info   ] hv_utils: TimeSync IC version 4.0
[21:00:00.870][Moby           ][Info   ] hv_vmbus: registering driver hv_balloon
[21:00:00.891][Moby           ][Info   ] oprofile: using timer interrupt.
[21:00:00.906][Moby           ][Info   ] GACT probability on
[21:00:00.916][Moby           ][Info   ] Mirror/redirect action on
[21:00:00.931][Moby           ][Info   ] Simple TC action Loaded
[21:00:00.941][Moby           ][Info   ] netem: version 1.3
[21:00:00.951][Moby           ][Info   ] u32 classifier
[21:00:00.985][Moby           ][Info   ]     Performance counters on
[21:00:00.996][Moby           ][Info   ]     input device check on
[21:00:01.006][Moby           ][Info   ]     Actions configured
[21:00:01.036][Moby           ][Info   ] Netfilter messages via NETLINK v0.30.
[21:00:01.055][Moby           ][Info   ] nfnl_acct: registering with nfnetlink.
[21:00:01.116][Moby           ][Info   ] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[21:00:01.141][Moby           ][Info   ] ctnetlink v0.93: registering with nfnetlink.
[21:00:01.176][Moby           ][Info   ] nf_tables: (c) 2007-2009 Patrick McHardy <kaber@trash.net>
[21:00:01.222][Moby           ][Info   ] nf_tables_compat: (c) 2012 Pablo Neira Ayuso <pablo@netfilter.org>
[21:00:01.256][Moby           ][Info   ] xt_time: kernel timezone is -0000
[21:00:01.272][Moby           ][Info   ] ip_set: protocol 6
[21:00:01.286][Moby           ][Info   ] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
[21:00:01.316][Moby           ][Info   ] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
[21:00:01.341][Moby           ][Info   ] IPVS: Creating netns size=2104 id=0
[21:00:01.361][Moby           ][Info   ] IPVS: ipvs loaded.
[21:00:01.377][Moby           ][Info   ] IPVS: [rr] scheduler registered.
[21:00:01.398][Moby           ][Info   ] IPVS: [wrr] scheduler registered.
[21:00:01.426][Moby           ][Info   ] IPVS: [lc] scheduler registered.
[21:00:01.446][Moby           ][Info   ] IPVS: [wlc] scheduler registered.
[21:00:01.474][Moby           ][Info   ] IPVS: [fo] scheduler registered.
[21:00:01.493][Moby           ][Info   ] IPVS: [ovf] scheduler registered.
[21:00:01.517][Moby           ][Info   ] IPVS: [lblc] scheduler registered.
[21:00:01.542][Moby           ][Info   ] IPVS: [lblcr] scheduler registered.
[21:00:01.574][Moby           ][Info   ] IPVS: [dh] scheduler registered.
[21:00:01.586][Moby           ][Info   ] IPVS: [sh] scheduler registered.
[21:00:01.602][Moby           ][Info   ] IPVS: [sed] scheduler registered.
[21:00:01.632][Moby           ][Info   ] IPVS: [nq] scheduler registered.
[21:00:01.652][Moby           ][Info   ] IPVS: ftp: loaded support on port[0] = 21
[21:00:01.679][Moby           ][Info   ] ipip: IPv4 and MPLS over IPv4 tunneling driver
[21:00:01.702][Moby           ][Info   ] gre: GRE over IPv4 demultiplexor driver
[21:00:01.727][Moby           ][Info   ] ip_gre: GRE over IPv4 tunneling driver
[21:00:01.742][Moby           ][Info   ] IPv4 over IPsec tunneling driver
[21:00:01.780][Moby           ][Info   ] ip_tables: (C) 2000-2006 Netfilter Core Team
[21:00:01.813][Moby           ][Info   ] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[21:00:01.852][Moby           ][Info   ] arp_tables: arp_tables: (C) 2002 David S. Miller
[21:00:01.871][Moby           ][Info   ] Initializing XFRM netlink socket
[21:00:01.902][Moby           ][Info   ] NET: Registered protocol family 10
[21:00:01.917][Moby           ][Info   ] mip6: Mobile IPv6
[21:00:01.952][Moby           ][Info   ] ip6_tables: (C) 2000-2006 Netfilter Core Team
[21:00:01.992][Moby           ][Info   ] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[21:00:02.032][Moby           ][Info   ] ip6_gre: GRE over IPv6 tunneling driver
[21:00:02.057][Moby           ][Info   ] NET: Registered protocol family 17
[21:00:02.083][Moby           ][Info   ] NET: Registered protocol family 15
[21:00:02.108][Moby           ][Info   ] Bridge firewalling registered
[21:00:02.123][Moby           ][Info   ] Ebtables v2.0 registered
[21:00:02.153][Moby           ][Info   ] l2tp_core: L2TP core driver, V2.0
[21:00:02.182][Moby           ][Info   ] l2tp_ppp: PPPoL2TP kernel driver, V2.0
[21:00:02.198][Moby           ][Info   ] 8021q: 802.1Q VLAN Support v1.8
[21:00:02.243][Moby           ][Info   ] 9pnet: Installing 9P2000 support
[21:00:02.428][Moby           ][Info   ] Key type dns_resolver registered
[21:00:02.491][Moby           ][Info   ] openvswitch: Open vSwitch switching datapath
[21:00:02.506][Moby           ][Info   ] hv_vmbus: registering driver hv_sock
[21:00:02.526][Moby           ][Info   ] NET: Registered protocol family 43
[21:00:02.541][Moby           ][Info   ] mpls_gso: MPLS GSO support
[21:00:02.566][Moby           ][Info   ] microcode: sig=0x40651, pf=0x1, revision=0xffffffff
[21:00:02.593][Moby           ][Info   ] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[21:00:02.623][Moby           ][Info   ] AVX2 version of gcm_enc/dec engaged.
[21:00:02.648][Moby           ][Info   ] AES CTR mode by8 optimization enabled
[21:00:02.663][Moby           ][Info   ] registered taskstats version 1
[21:00:02.689][Moby           ][Info   ] Key type big_key registered
[21:00:02.709][Moby           ][Info   ] Key type encrypted registered
[21:00:02.785][Moby           ][Info   ] rtc_cmos 00:00: setting system clock to 2017-03-02 21:00:01 UTC (1488488401)
[21:00:02.853][Moby           ][Info   ] Freeing unused kernel memory: 1392K (ffffffffbdf62000 – ffffffffbe0be000)
[21:00:02.964][Moby           ][Info   ] Write protecting the kernel read-only data: 14336k
[21:00:03.083][Moby           ][Info   ] Freeing unused kernel memory: 1728K (ffff9d6434850000 – ffff9d6434a00000)
[21:00:03.937][Moby           ][Info   ] Freeing unused kernel memory: 1236K (ffff9d6434ccb000 – ffff9d6434e00000)
[21:00:03.937][Moby           ][Info   ]
[21:00:03.942][Moby           ][Info   ]    OpenRC 0.21.7.e3f10ac is starting up Linux 4.9.12-moby (x86_64)
[21:00:03.942][Moby           ][Info   ]
[21:00:03.942][Moby           ][Info   ]  * Mounting /proc … [ ok ]
[21:00:03.942][Moby           ][Info   ]  * Mounting /run … * /run/openrc: creating directory
[21:00:03.942][Moby           ][Info   ]  * /run/lock: creating directory
[21:00:03.942][Moby           ][Info   ]  * /run/lock: correcting owner
[21:00:03.942][Moby           ][Info   ]  * Caching service dependencies … [ ok ]
[21:00:03.942][Moby           ][Info   ]  * Mounting /sys … [ ok ]
[21:00:03.942][Moby           ][Info   ]  * Mounting security filesystem … [ ok ]
[21:00:03.942][Moby           ][Info   ]  * Mounting debug filesystem … [ ok ]
[21:00:03.942][Moby           ][Info   ]  * Mounting fuse control filesystem … [ ok ]
[21:00:03.942][Moby           ][Info   ]  * Mounting persistent storage (pstore) filesystem … [ ok ]
[21:00:03.942][Moby           ][Info   ]  * Mounting cgroup filesystem … [ ok ]
[21:00:03.942][Moby           ][Info   ]  * Mounting devtmpfs on /dev … [ ok ]
[21:00:04.143][Moby           ][Info   ]  * Mounting /dev/mqueue … [ ok ]
[21:00:04.223][Moby           ][Info   ]  * Mounting /dev/pts … [ ok ]
[21:00:04.263][Moby           ][Info   ]  * Mounting /dev/shm … [ ok ]
[21:00:04.485][Moby           ][Info   ]  * Starting busybox mdev … [ ok ]
[21:00:04.663][Moby           ][Info   ]  * Configuring host block device …/dev/sda1: recovering journal
[21:00:06.592][Moby           ][Info   ] /dev/sda1: clean, 243534/3932160 files, 2688511/15728384 blocks
[21:00:06.792][Moby           ][Info   ]  [ ok ]
[21:00:06.957][Moby           ][Info   ]  * Autodetection of hardware disabled from boot cmdline
[21:00:07.087][Moby           ][Info   ] /lib/rc/sh/openrc-run.sh: line 250: can’t create /sys/fs/cgroup/openrc/fsck/tasks: nonexistent directory
[21:00:07.162][Moby           ][Info   ]  * Remounting filesystems … [ ok ]
[21:00:07.636][Moby           ][Info   ]  * Mounting local filesystems … [ ok ]
[21:00:07.774][Moby           ][Info   ]  * Setting system clock using the hardware clock [UTC] … [ ok ]
[21:00:07.857][Moby           ][Info   ]  * Setting hostname … [ ok ]
[21:00:08.031][Moby           ][Info   ]  * Creating user login records … [ ok ]
[21:00:08.116][Moby           ][Info   ]  * Starting vsock proxy … [ ok ]
[21:00:08.155][Moby           ][Info   ]  * sysklogd -> start: syslogd … [ ok ]
[21:00:08.354][Linux          ][Info   ] Vsudd is reachable!
[21:00:08.359][ApiProxy       ][Info   ] Starting C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe -VM=759575fe-c030-478c-b5b5-07dc2bfbdae0
[21:00:08.364][ApiProxy       ][Info   ] Started
[21:00:08.817][ApiProxy       ][Info   ] docker proxy (on deprecated port): ready
[21:00:08.822][ApiProxy       ][Info   ] docker proxy: ready
[21:00:08.822][ApiProxy       ][Info   ] proxy >> GET /_ping
[21:00:08.822][ApiProxy       ][Info   ] Dial Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:08.822][DockerDaemonChecker][Error  ] Docker daemon is not running
[21:00:08.822][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:08.822][ApiProxy       ][Info   ] error reading response from Docker:  HvSocket has already been closed
[21:00:08.822][ApiProxy       ][Info   ] proxy >> GET /v1.26/containers/json
[21:00:08.822][ApiProxy       ][Info   ] Dial Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:08.822][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:08.822][ApiProxy       ][Info   ] error reading response from Docker:  HvSocket has already been closed
[21:00:09.407][Moby           ][Info   ]  * sysklogd -> start: klogd … [ ok ]
[21:00:09.710][Moby           ][Info   ]  * Starting busybox crond … [ ok ]
[21:00:09.780][Moby           ][Info   ]  * Mounting misc binary format filesystem … [ ok ]
[21:00:09.892][ApiProxy       ][Info   ] proxy >> GET /_ping
[21:00:09.895][ApiProxy       ][Info   ] Dial Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:09.934][Moby           ][Info   ]  * Setting sysfs variables … [ ok ]
[21:00:09.943][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:09.947][ApiProxy       ][Info   ] error reading response from Docker:  HvSocket has already been closed
[21:00:09.953][ApiProxy       ][Info   ] proxy >> GET /v1.26/containers/json
[21:00:09.954][ApiProxy       ][Info   ] Dial Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:09.957][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:09.960][ApiProxy       ][Info   ] error reading response from Docker:  HvSocket has already been closed
[21:00:09.980][DockerDaemonChecker][Error  ] Docker daemon is not running
[21:00:10.017][Moby           ][Info   ]  * Starting local … [ ok ]
[21:00:10.393][Moby           ][Info   ]  * Setting up database (Windows) …/sbin/9pmount-vsock: starting in listening mode with serviceid=C378280D-DA14-42C8-A24E-0DE92A1028E2, tag=db, path=/tmp/db
[21:00:11.037][ApiProxy       ][Info   ] proxy >> GET /_ping
[21:00:11.038][ApiProxy       ][Info   ] Dial Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:11.039][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:11.044][ApiProxy       ][Info   ] error reading response from Docker:  HvSocket has already been closed
[21:00:11.049][ApiProxy       ][Info   ] proxy >> GET /v1.26/containers/json
[21:00:11.049][ApiProxy       ][Info   ] Dial Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:11.052][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 759575fe-c030-478c-b5b5-07dc2bfbdae0:23a432c2-537a-4291-bcb5-d62504644739
[21:00:11.064][ApiProxy       ][Info   ] error reading response from Docker:  HvSocket has already been closed
[21:00:11.069][DockerDaemonChecker][Error  ] Docker daemon is not running
[21:00:11.250][DataKit        ][Info   ] com.docker.db.exe: accepted a new connection on hyperv-connect://759575fe-c030-478c-b5b5-07dc2bfbdae0
[21:00:11.308][DataKit        ][Info   ] com.docker.db.exe: Using protocol TwoThousand msize 4096
[21:00:11.499][Moby           ][Info   ] /sbin/9pmount-vsock: Connect from: 00000000-0000-0000-0000-000000000000:d77ea67f-ff50-11e6-a5ab-6002920692fc
[21:00:11.586][Moby           ][Info   ] /sbin/9pmount-vsock: mount successful for serviceid=C378280D-DA14-42C8-A24E-0DE92A1028E2 tag=db path=/tmp/db
[21:00:11.968][DataKit        ][Error  ] com.docker.db.exe: Hvsock.read raised Unix.Unix_error(Unix.ECONNABORTED, “read”, “”): returning `Eof
[21:00:11.982][Moby           ][Info   ]  [ ok ]

Start with Docker for windows too  => It’s Cool 😉

UPDATE Microsoft Azure Storage Explorer Tool #Azure #Storage #Cloud

What’s New in Microsoft Azure Storage Explorer Tool version 0.8.9 :

• New
  • Storage Explorer 0.8.9 will automatically download the latest version for updates.
  • Hotfix: using a portal generated SAS URI to attach a storage account would result in an error.
  • You can now create, manage, and promote blob snapshots.
  • You can now sign in to Azure China, Azure Germany, and Azure US Government accounts.
  • You can now change the zoom level. Use the options in the View menu to Zoom In, Zoom Out, and Reset Zoom.
  • Unicode characters are now supported in user metadata for blobs and files.
  • Accessibility improvements.
  • The next version’s release notes can be viewed from the update notification. You can also view the current release notes from the Help menu.
• Fixes
  • Fixed: the version number is now correctly displayed in Control Panel on Windows
  • Fixed: search is no longer limited to 50,000 nodes
  • Fixed: upload to a file share spun forever if the destination directory did not already exist
  • Fixed: improved stability for long uploads and downloads
• Known Issues
  • While zoomed in or out, the zoom level may momentarily reset to the default level.
  • Quick Access only works with subscription based items. Local resources or resources attached via key or SAS token are not supported in this release.
  • It may take Quick Access a few seconds to navigate to the target resource, depending on how many resources you have.
  • Having more than 3 groups of blobs or files uploading at the same time may cause errors.

You can download the Microsoft Azure Storage Explorer Tool here

 

#Microsoft AzureStack Technical Preview 3 Available for Download #AzureStack #Cloud

Azure Stack Architecture

Today Microsoft released Azure Stack Technical Preview 3 for customers to do Proof of Concept (POC) with Azure Cloud Platform Services in your own Datacenter.

You can download Microsoft AzureStack TP3 here

What’s new in Azure Stack TP3 ?

Content, services, and tools

• Active Directory Federation Services (AD FS) support provides identity options for scenarios where network connectivity is limited or intermittent.
• You can use Azure Virtual Machine Scale Sets to provide managed scale out of workloads.
• Use Azure D-Series VM sizes for increased performance and consistency.
• Deploy and create templates with Temp Disks that are consistent with Azure.
• Marketplace Syndication allows you to use content from the Azure Marketplace and make available in Azure Stack. 

Infrastructure and operations

• Isolated administrative and user portals and APIs provide enhanced security.
• Use enhanced infrastructure management functionality, such as improved alerting.
• Using the Windows Azure Pack connector, you can view and manage IaaS virtual machines that are hosted on a Cloud Platform System (CPS) stamp. For this preview release, you can try this only with a CPS environment and additional configuration is required.

More Technical documentation of Azure Stack TP3 and Deployment :

What is Azure Stack Technical Preview 3?

You can download here a complete Azure Stack documentation in PDF format

AzureStack Cloud Tools on GitHub

 

#Microsoft OMS Service Map for Hybrid IT Management #MSOMS #Azure #Linux #HybridCloud

Service Map in #MSOMS automatically builds a common reference map of dependencies across your servers, processes, and third-party services. It discovers and maps all TCP dependencies, identifying surprise connections, remote third-party systems you depend on, and dependencies to traditional dark areas of your network such as Active Directory. Service Map discovers failed network connections that your managed systems are attempting to make, helping you identify potential server misconfiguration, service outages, and network issues.

Microsoft Operations Management Suite

OMS Service Map Overview of my Demo Environment

Machine Changes on HybridCloud01 Server

You now can see that the Previous Service State Running is changed in Stopped.

When you go more in details and look at the log Search in this event :

When this event is important to you you can make an OMS Alert on this Change :

With OMS Alert you can take actions like :

With Microsoft OMS Runbooks you can make Automation solutions for Hybrid IT Events.

Servicemap Summary

Servicemap Server Properties

OMS Service Map Performance

OMS Service Map Updates

More information about using Awesome Service Map solution in Operations Management Suite (OMS) you can find here

Configuring Service Map solution in Operations Management Suite (OMS)

Service Map gets its data from the Microsoft Dependency Agent. The Dependency Agent is dependent on the OMS Agent for its connections to OMS. This means that a server must have the OMS Agent installed and configured first, and then the Dependency Agent can be installed. The following table describes the connected sources that are supported by the Service Map solution.

Here you can find more information about configuring OMS Service Maps

Operations Management Suite (OMS) SDK

I like Microsoft OMS Service Map a lot because you can see the relations between Servers, Services, Applications in a Hybrid IT environment and
get proactive alerts to take action to keep your Hybrid Datacenters Healthy 🙂

#MSOMS Rocks
#MVPbuzz

UPDATE #Docker for Windows is Available #Containers #Azure #Cloud #DevOps #MSOMS

 

CONTAINERS

Containers include the application and all of its dependencies –but share the kernel with other containers, running as isolated processes in user space on the host operating system. Docker containers are not tied to any specific infrastructure: they run on any computer, on any infrastructure, and in any cloud.

Here you find the Docker command Reference guide

Get started with Docker Containers for Windows here

Here you find all the Docker documentation Online

Monitoring your Containers with Microsoft Operations Management Suite for Hybrid IT Management :

See the Blogpost of #MSOMS

 

UPDATE #Microsoft Azure Storage Explorer version with Blob Snapshots ! #Azure #Storage #DevOps

Microsoft Azure Storage Explorer version 0.8.8

Microsoft Azure Storage Explorer  is a standalone app from Microsoft that allows you to easily work with Azure Storage data on Windows, macOS and Linux.

New

• You can now create, manage, and promote blob snapshots.
• Storage Explorer will now automatically download the latest version when it is available.
• You can now sign in to Azure China, Azure Germany, and Azure US Government accounts.
• You can now change the zoom level. Use the options in the View menu to Zoom In, Zoom Out, and Reset Zoom.
• Unicode characters are now supported in user metadata for blobs and files.
• Accessibility improvements.
• The next version’s release notes can be viewed from the update notification. You can also view the current release notes from the Help menu.

Fixes

• Fixed: the version number is now correctly displayed in Control Panel on Windows
• Fixed: search is no longer limited to 50,000 nodes
• Fixed: upload to a file share spun forever if the destination directory did not already exist
• Fixed: improved stability for long uploads and downloads

You can download the Microsoft Azure Storage Explorer here