Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Steve Lasker
Dick Butkus is arguably one of the best linebackers ever to play, possessing strength, agility and quickness to cover running backs and tight ends on the same play. He played for the Bears from 1965 to 1973, making seven Pro Bowl teams, collecting 22 inte
Dick Butkus is arguably one of the best linebackers ever to play, possessing strength, agility and quickness to cover running backs and tight ends on the same play. He played for the Bears from 1965 to 1973, making seven Pro Bowl teams, collecting 22 interceptions and recovering 27 fumbles. He was elected to the Hall of Fame in 1979, his first year of eligibility. (Steve lasker/Chicago Tribune/TNS)
Dick Butkus is arguably one of the best linebackers ever to play, possessing strength, agility and quickness to cover running backs and tight ends on the same play. He played for the Bears from 1965 to 1973, making seven Pro Bowl teams, collecting 22 inte
Skip to main contentSkip to main content Register for more free articles. Please subscribe to keep reading. You can cancel at any time. *offer available for new customers only Special introductory price! Enjoy these exclusive benefits: Unlimited access to our E-Edition Unlimited articles on winonadailynews.com and our mobile app FREE Access to Newspapers.com archives (last 2 years) Games and puzzles online You have permission to edit this image. You don't have any notifications.
Dick Butkus is arguably one of the best linebackers ever to play, possessing strength, agility and quickness to cover running backs and tight ends on the same play. He played for the Bears from 1965 to 1973, making seven Pro Bowl teams, collecting 22 inte
Skip to main contentSkip to main content Register for more free articles. Please subscribe to keep reading. You can cancel at any time. *offer available for new customers only Special introductory price! Enjoy these exclusive benefits: Unlimited access to our E-Edition Unlimited articles on beatricedailysun.com and our mobile app FREE Access to Newspapers.com archives (last 2 years) Games and puzzles online You have permission to edit this image. You don't have any notifications.
Azure Container Registry: the first cloud registry to support the OCI Specifications 1.1
Azure Container Registry (ACR) now has support for the OCI v1.1-RC Specifications. The update continues the journey of standardizing OCI Distribution-based registries to store, discover and distribute all types of artifacts, including adding references to existing images and other OCI artifacts. It started 4 years ago when ACR added support for Helm Chart distribution using the existing registry services users have already configured for their secure environments.
Roles and Responsibilities of Signing, SBoMs, and Security Scanners
As cloud-native development continues to automate the consumption of upstream content providers, the ability for automation to make real-time, informed decisions becomes critical to keep the automation wheels spinning. The speed of development and consumption has reached the point where cracks in the system are always present, even if not immediately seen. The ability to leverage new information against facts on artifacts already in our environments are key aspects of analysis.
Deploying ASP.NET Core applications using Docker Containers
It was helpful in a certain way. I still try to get my head around how my variety ASP.NET Core projects could benefit using Docker Containers. If they could at all. I am using VMs where each of them has got a few websites and trying to learn when would be the good time to consider using Docker Containers, how much it would improve the deployment or whatever as I am quite happy even with the current form of deployment. Or when there is not point to use Docker Containers at all.
Azure Container Registry: Mitigating data exfiltration with dedicated data endpoints
Steve Lasker Program Manager, Azure Container Registry Azure Container Registry announces dedicated data endpoints, enabling tightly scoped client firewall rules to specific registries, minimizing data exfiltration concerns. Pulling content from a registry involves two endpoints: Registry endpoint, often referred to as the login URL, used for authentication and content discovery.
Azure Container Registry Private Link support preview for virtual networks
Azure Container Registry announces preview support for Azure Private Link, a means to limit network traffic of resources within the Azure network. With Private Link, the registry endpoints are assigned private IP addresses, routing traffic within a customer-defined virtual network. Private network support has been one of the top customer asks, allowing customers to benefit from the Azure management of their registry while benefiting from tightly controlled network ingress and egress.
Microsoft container registry unaffected by the recent Docker Hub data exposure
Docker recently announced Docker Hub had a brief security exposure that enabled unauthorized access to a Docker Hub database, exposing 190k Hub accounts and their associated GitHub tokens for automated builds. While initial information led people to believe the hashes of the accounts could lead to image:tags being updated with vulnerabilities, including official and microsoft/ org images, this was not the case.
Azure Container Registry now supports Singularity Image Format containers
Azure and Sylabs announced today a new collaboration which enables Singularity container images to be stored in registries supporting the Open Container Initiative (OCI) Distribution Specification. Singularity version 3.0 defines a new secure Singularity Image Format (SIF).
Azure Container Registry virtual network and Firewall rules preview support
While Azure Container Registry (ACR) supports user and headless-service account authentication, customers have expressed their requirements for limiting public endpoint access. Customers can now limit registry access within an Azure Virtual Network (VNet), as well as whitelist IP addresses and ranges for on-premises services. VNet and Firewall rules are supported with virtual machines (VM) and Azure Kubernetes Services (AKS).
Moving the cheese - StevenLasker.blog
Moving the cheese – StevenLasker.blog Microsoft is retiring personal msdn blogs. As a result, I've moved all my blog content to https://StevenLasker.blog I hope you'll keep the great feedback coming there. Steve
Azure Container Registry: Public preview of Helm Chart Repositories and more
With Azure Container Registry (ACR), you can easily store and manage container images for Azure deployments in a central registry. Today we are excited to add native Helm repository support and validation workflows, with ACR tasks and Docker’s content trust, to provide a more integrated container lifecycle management experience.
ACR Build (Preview) Now Supported In All Public Regions
ACR Build, a native container build capability of the Azure Container Registry is now available in all regions ACR is available. That's 23 regions worldwide as of July 23rd 2018. ACR Build enables network close builds, alongside your container registry. While docker has an efficient image layering scheme, image layers can grow in size. Reducing the network distance your image pull and push operations must travel is key to improving reliability, speed and reducing network egress costs.
Azure Container Registry Build Supports All Windows Versions (Preview of Preview)
ACR Build, a cloud-native container build capability of the Azure Container Registry now supports all supported versions of Windows Containers. In May of 2018, Azure announced ACR Build (Preview), a component of Azure's OS & Framework Container Life-cycle Management Today, we wanted to give customers early access to Windows Builds, in addition to the Linux and ARM builds customers could do since last May.
Key Differences between VM and Container Vulnerability Scanning
As we explore the various options for integrating vulnerability scanning into containers running in Azure, we encountered many different approaches and requests. I was initially writing a document for internal discussions, outlining some of our internal goals for how we want to think about container security, and why we might take one approach or another.
ACR Build OS & Framework Patching Now Supports Docker Hub
In May we announced the public preview of ACR Build, enabling OS & Framework patching. When we announced the preview, only Azure Container Registries were supported for base image update notifications. With DockerCon starting this week, it's only appropriate we add support for base in Docker Hub. When completes, the base images dependencies are dynamically discovered.
How ACR Build Id’s are generated
As you use ACR Build, for OS & Framework patching, native container builds, or validating a docker build without having the docker client installed, you may be wondering, what is the format for those alpha-numeric Build id's. The short answer is it's based on the region the build was executed upon, and a base 32, alpha-numeric sequence to provide independent execution, with multi-region fault tolerance. For some background why we chose this solution...
Azure Container Registry makes geo-replication generally available, adding lifecycle management capabilities
Container based applications are growing at a strong pace, as result, we are seeing an increasing number of customers using Azure Container Registry to manage their Linux and Windows container images. Azure Container Registry provides a network-close, private registry and integrates well with orchestrators hosted in Azure as well as other Azure Services including Service Fabric, Azure App Service, IoT, Machine Learning, and more to come.
Building Resilient Microservices with .NET Core and Azure Container Services (AKS)
Microservices are highly scalable, resilient, and composable units of deployment for modern applications. But building them is hard. There are a lot of development and deployment considerations to take into account.
test
This content is password protected. To view it please enter your password below:
Docker Tagging: Best practices for tagging and versioning docker images
In any new tech, there are lots of thoughts around “best practices”. When a tech is new, what makes a best practice? Working at Microsoft, running the Azure Container Registry (ACR), talking with lots of customers, some that use Azure and some that don’t, we’ve had a lot of exposure to what customers have encountered. We’ve been working on a number of scenarios, including container life cycle management and OS & Framework patching with containers. This has surfaced a number of interesting issues.
Relaxing ACR storage limits, with tools to self manage
When we created the tiered SKUs for ACR, we built the three tiers with the following scenarios in mind: The goal was never to force someone up a tier, beyond the basic tier. Or worse, cause a build failure if a registry filled up. Well, we all learn. 𙂠It seems customers were quick to enable automation - awesome!. And are quickly filling up their registries.
Working with ACR Geo-replication notifications
Azure Container Registry geo-replication enables a single control plane across the global footprint of Azure. You can opt into the regions you'd like your registry to have a network-close/local experience. However, there are some important aspects to consider. ACR Geo-replication is multi-master. You can push to any region, and ACR will replicate the manifests and layers to all other regions you've opted into. However, replication does take some time. Time, based on the size of the image layers.
OS & Framework Patching with Docker Containers - a paradigm shift
Thinking of containers, we think of the easy packaging of our app, along with its dependencies. The dockerfile FROM defines the base image used, with the contents copied or restored into the image. We now have a generic package format that can be deployed onto multiple hosts. No longer must the host know about what version of the stack that's used, nor even the version of the operating system. And, we can deploy any configuration we need, unique to our container.
.NET and MultiStage Dockerfiles
A while back I talked about building optimized docker images. (Building Optimized Docker Images with ASP.NET Core) With compiled runtimes like Go, Java and .NET, you'll want to first compile your code before having a binary that can be run. The components required to compile your code are not required to run your code. And the SDKs can be quite big, not to mention any potential attack surface area. The best practice has been to build docker images in steps.
Deploying Docker Images from the Azure Container Registry to Azure Container Instances
In just a few minutes you can easily deploy Docker Container Images using just a context menu from the repositories blade of the Azure Container Registry. Azure Container Instances allow you to deploy Container Images directly without first provisioning VMs, Container Orchestrators, or any other container infrastructure. With Azure Container Instances, you pay just for what you use.
New Azure Container Registry SKUs
We recently released a preview of new Azure Container Registry SKUs, along with an overview on Channel 9 Video with Seth Juarez. One question that's come up; what are the differences in the SKUs. This enabled the most common scenarios, and provided a GA product as we heard customers needed a private registry, network-close to their deployments that wasn't in preview. The March GA release placed the storage of the registry in the customers subscription.
Azure Container Registry adds individual identity, webhooks, and delete capabilities
The Azure Container Registry team is excited to share a preview of new Container Registry SKUs with more capabilities and features. The new preview of Azure Container Registry managed tier is available in 3 options including Basic, Standard, and Premium. These new container registries are available in preview within 3 regions including East US, West Europe, and West Central US. Support for other regions will roll out over the course of the following weeks based on feedback.
Docker for Windows, Creators Update and Volume Sharing Linux Containers
If you’re attempting to use Volume Sharing with Docker for Windows after you’ve installed the Creators Update, you may get errors indicating a Firewall Port must be opened. This combination of the Creators Update, Domain Joined machines and enabling volume sharing has had a recent regression we’re working to resolve. Note: this only applies to Linux Volume Sharing. Be sure Docker for Windows is set to Linux. This should get you going. If not, please help us understand what’s unique.
Azure Container Registry now generally available
Companies of all sizes are embracing containers as a fast and portable way to lift, shift and modernize into cloud-native apps. As part of this process, customers need a way to store and manage images for all types of container deployments. In November, we announced the preview of Azure Container Registry, which enables developers to create and maintain Azure container registries to store and manage private Docker container images.
.NET Docker Development with Visual Studio 2017
Develop .NET Framework Apps with Windows Server Core Containers and .NET Core with Linux Containers with the productivity you'd expect from Visual Studio, while maintaining the native Docker experienc
Balancing change: feedback + learning / impact to customers = change
I was reading a post about the frustration a customer had around the constant change. First, I do apologize for the frustration as it is difficult to continually learn new things when the things you’ve learned keep changing. With each change, we balance the impact it will have on our existing customers, the challenges they’re currently facing, what we’re learning from our previous releases, and the impact we can have for new customers.
Visual Studio Docker tools support for Visual Studio 2015 and 2017
With the Visual Studio 2017 RC release, we’ve started down the path to finally shipping an official version of Visual Studio Docker tools; enabling developers to locally develop and debug containerized workloads. The latest Visual Studio 2017 RC Docker Tools added a number of anticipated features: We also spent a lot of time improving the overall quality There are bunch of other great features and quality items that went in to the Visual Studio RC release.
Azure Container Registry User Accounts; Single, Multi, Admin and Service Principals
The Azure Container Registry went into public preview yesterday. We’re excited to add this core platform feature for the breadth of container deployments being added to Azure. These include Azure Container Service, Azure Service Fabric, Azure App Service and Azure Batch, …as of now. More are coming… When designing the Azure Container Registry, we felt it important to maintain common CLI support, such as using and . Docker login is a basic auth flow, requiring a username and password.
Azure Container Registry preview
In today’s cloud-first world, applications are the vital ingredients that fuel innovation and productivity. Whether you are lifting and shifting apps to the cloud or building new cloud-native apps, containers are an attractive option to efficiently package software applications and deploy them as quickly as the business demands. Containers empower engineers to focus on innovation and new features rather than worry about how their code will be deployed.
Patching Docker Containers - The Balance of Secure and Functional
The cloud is evolving at a rapid pace. We have increasingly more options for how to host and run the tools that empower our employees, customers, friends and family. New apps depend on the capabilities of underlying sdks, frameworks, services, platforms which depend on operating systems and hardware. For each layer of this stack, things are constantly moving. We want and need them to move and evolve. And, while our “apps” evolve, bugs surface. Some simple.
Building Optimized Docker Images with ASP.NET Core
If you’re exploring docker, you’ll often see dockerfiles that demonstrate the simplicity of building a docker image by copying your source into a container and voila, you have a docker image with the environment packaged with your app. While very true, and very cool, there are big optimizations to be had. .NET has a long history of productivity. When working with server based deployments, customers wanted fast ways to deploy updates.
Running Scripts in a Docker Container from Windows- CR or CRLF
For Ignite 2016, I’m building out a demo for building your .NET Core code in a container. This is part of our story behind building optimized images. But, before I get to that post, what started out as something simple, something I’ve done on my Mac fairly easily turned into a frustrating experience from Windows. It turns out sending files through the Volume Mounted wormhole can be more difficult than you might think.
Docker for Windows, Network Shares and $ in you password
If you’ve been using our docker tools you’ve noticed we depend highly on network sharing for Docker for Windows. For the Linux host to mount your Windows drives, you need to provide a username/password. What you may not realize is Linux has some special characters it may not always handle. Short story: if you’re having trouble with volume sharing & Docker for Windows, make sure you don’t have a $ in your password. ” and ; are also suspect at this point.
Configuring Docker for Windows Shared Drives / Volum Mounting with AD
If you’ve had a chance to work with the Docker for Windows beta, you’ve seen the promise for how much easier this can be compared to VirtualBox. That said, there are still some issues, thus the beta tag. One such issue is volume mounting. If you work for an enterprise, you more than likely log into your machine with corporate/domain credentials. When you configure Docker for Windows Shared Drives, you’ll get prompted with your credentials. You most likely entered your corporate domain account.
Building .NET Core Linux Docker Images with Visual Studio Team Services
If you’ve been wondering how to build a .NET Core app into a Docker image using VSTS, well here’s the current steps as of June 2016. You’ll need the following to complete this walk through To build a .NET Core Docker Image, you’ll need a VSTS Build Agent.
Defaulting to Docker for Windows with Docker Tools for Visual Studio
When using Docker Tools for Visual Studio, we default the Docker host to use Docker Toolbox. Or, more specifically, we set the default docker machine to be named default, which people typically create a VirtualBox host named default. This is documented here. Docker for Windows doesn’t use Docker-Machine, rather assumes no HOST entries are set. To make Docker Tools for Visual Studio work with Docker for Windows, we’ll need to change the host.
Docker For Windows Beta Released
Docker For Windows Beta Released Today, docker announced and released a replacement for Docker Toolbox. There are many enhancements, including my top …6 Works with Hyper-V Docker Toolbox utilized VirtualBox. An alternate Virtualization technology that meant developers had to disable Hyper-V. Which means they can’t run VMs or the various developer emulators, which also use Hyper-V Starts automatically – no more docker-machine start default The docker process will start automatically, by default.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Steve
Contact Steve, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack