John Starks (Microsoft) & Arnaud Porterie (Docker) present the ongoing work to support Docker on Windows platforms using Windows Server Containers and Hyper-V Containers.
This slide deck is about modern trends in Virtualization called Containers, how docker mastered it and how it makes way into Windows operating systems. The slides also help to get started working with containers using Azure.
runC: The little engine that could (run Docker containers) by Docker Captain ...Docker, Inc.
With the announcement of the OCI by Solomon Hykes at last summer's DockerCon, a Docker-contributed reference implementation of the OCI spec, called runC, was born. While some of you may have tried runC or have a history of poking at the OS layer integration library to Linux namespaces, cgroups and the like (known as libcontainer), many of you may not know what runC offers. In this talk Phil Estes, Docker engine maintainer who has also contributed to libcontainer and runC, will show what's possible using runC as a lightweight and fast runtime environment to experiment with lower-level features of the container runtime. Phil will introduce a conversion tool called "riddler", which can inspect and convert container configurations from Docker into the proper OCI configuration bundle for easy conversion between the two environments. He'll also demonstrate how to make custom configurations for trying out security features like user namespaces and seccomp profiles.
Container Security: How We Got Here and Where We're GoingPhil Estes
A talk given on Wednesday, Nov. 16th at DefragCon (DefragX) on a historical perspective on container security with a look to where we're going in the future.
Tokyo OpenStack Summit 2015: Unraveling Docker SecurityPhil Estes
A Docker security talk that Salman Baset and Phil Estes presented at the Tokyo OpenStack Summit on October 29th, 2015. In this talk we provided an overview of the security constraints available to Docker cloud operators and users and then walked through a "lessons learned" from experiences operating IBM's public Bluemix container cloud based on Docker container technology.
How Secure Is Your Container? ContainerCon Berlin 2016Phil Estes
A conference talk at ContainerCon Europe in Berlin, Germany, given on October 5th, 2016. This is a slightly modified version of my talk first used at Docker London in July 2016.
Rooting Out Root: User namespaces in DockerPhil Estes
This talk on the progress to bring user namespace support into Docker was presented by Phil Estes at LinuxCon/ContainerCon 2015 on Wednesday, Aug. 19th, 2015
This document discusses Docker, an open-source container platform. It begins with a quick survey asking how familiar people are with Docker. It then defines Docker as allowing applications to be packaged into standardized units called containers that are portable and self-sufficient. The document outlines some benefits of containers like speed and small footprint. It compares containers to virtual machines and explains key components that enable containers like namespaces and control groups. Finally, it provides some basic Docker commands and examples of using Docker to package and run applications.
Dojo given at ESEI, Uvigo.
The slides include a set of great slides from a presentation made by Elvin Sindrilaru at CERN.
Docker is an open platform for building, shipping and running distributed applications. It gives programmers, development teams and operations engineers the common toolbox they need to take advantage of the distributed and networked nature of modern applications.
This document provides an introduction to Docker. It discusses key Docker concepts like OS virtualization using containers as opposed to virtual machines. Containers isolate processes and filesystems using cgroups, namespaces and UnionFS. Namespaces provide isolation for processes, networking, mounts etc. Cgroups are used to limit, account and isolate resource usage. The document also covers Docker storage and networking as well as security best practices.
Presentation on the Linux namespaces and system calls used to provide container isolation with Docker. Presented in March 2015 at http://www.meetup.com/Docker-Phoenix/ in Tempe, Arizona.
Just as the roles of CIOs and CTOs have needed to rapidly evolve along with the pace of technology, it is now becoming critically important for lawyers to understand emerging software security challenges.
Container security involves securing containers at both the host and application level. At the host level, Linux technologies like namespaces, cgroups, SELinux, and seccomp provide isolation between containers. Container images are also scanned for vulnerabilities. The OpenShift platform provides additional security features like role-based access control, network policies, encrypted communications, and controls over privileged containers and storage. Application security best practices within containers include using HTTPS, securing secrets, and API management tools.
An introduction to contianers and Docker for PHP developersRobert McFrazier
This document provides an introduction to containers and Docker for PHP developers. It defines Linux containers and their key components like namespaces and control groups. It explains that Docker is a container technology that packages applications and dependencies into standardized units. Docker Compose is introduced as a tool to define and run multi-container applications with Docker. Vagrant is described as a way to provide a Linux Docker host and shared folders. The document concludes by noting Docker's focus on container deployment and providing references for further information.
Introduction to Containers and Docker for PHP developersRobert McFrazier
This document provides an introduction to containers and Docker for PHP developers. It defines key concepts like namespaces and control groups that enable Linux containers. Docker is described as a container technology that packages applications and dependencies into standardized units. Docker Compose is a tool for defining and running multi-container apps with Docker. Vagrant is included to supply a Docker host and enable shared folders and port forwarding. The document outlines installing Docker and Docker Compose and distinguishes between images and containers.
Containerd - core container runtime component Docker, Inc.
Docker extracted its core container runtime component called containerd and donated it to an open source community project to accelerate innovation across the ecosystem. Containerd provides the core primitives to manage containers on Linux and Windows hosts and will be fully compliant with the Open Container Initiative standard. Major container platforms like Docker will use containerd as their core runtime component to provide a "boring" infrastructure component and allow for greater cross-platform compatibility and collaboration.
Docker Security and Orchestration for DevSecOps winsSharath Kumar
Dockers have literally transformed product deployment across the software industry. It makes traditional deployments a lot easier and supplements paradigms like Virtual Machines and Hypervisors.
While Dockers make packaging and deployments relatively simple, securing them continues to be a challenge especially when faced with Docker specific security threats such as Dockerization daemon, shared kernel and other shared resources like network and the filesystem.
Securing Dockerized deployments and orchestrating them IS, and WILL remain a key challenge for several Security practitioners and DevOps engineers.
Managing Open Source software in the Docker era nexB Inc.
Heather Meeker from O'Melveny & Myers and Michael Herzog from nexB discuss the specific impact of Docker on open source software governance and compliance.
containerd summit - Deep Dive into containerdDocker, Inc.
containerd is an industry-standard core container runtime with an emphasis on simplicity, robustness and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc..
containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users.
containerd includes a daemon exposing gRPC API over a local UNIX socket. The API is a low-level one designed for higher layers to wrap and extend. It also includes a barebone CLI (ctr) designed specifically for development and debugging purpose. It uses runC to run containers according to the OCI specification. The code can be found on GitHub, and here are the contribution guidelines.
containerd is based on the Docker Engine’s core container runtime to benefit from its maturity and existing contributors.
This presentation provides an overview of the different BSD operating systems for Linux users. It discusses the key differences between BSD and Linux, such as the release engineering process, package management, and unique features of each BSD like jails, ZFS, and DTrace. The presentation recommends some books for learning more about BSD and concludes by inviting questions.
The document discusses container security, providing advantages and disadvantages of containers as well as threats. It outlines different approaches to container security including host-based methods using namespaces, control groups, and capabilities as well as container-based scanning and digital signatures. Third-party security tools are also mentioned. The document concludes with examples of using containers for microservices and network policies for protection.
The document provides a summary of developments in 2012 for several BSD operating systems, including FreeBSD, NetBSD, OpenBSD, DragonFly BSD, and PC-BSD. It discusses their release schedules and highlights of new features. It also summarizes activities of the FreeBSD and NetBSD foundations in supporting development work and events.
This document summarizes a presentation on container security given by Phil Estes. It identifies several threat vectors for containers including risks from individual containers, interactions between containers, external attacks, and application security issues. It then outlines various security tools and features in Docker like cgroups, Linux Security Modules, capabilities, seccomp, and user namespaces that can help mitigate these threats. Finally, it discusses some future directions for improving container security through more secure defaults, image signing, and network security enhancements.
This document provides an overview of Docker containers, including what they are, how they differ from virtual machines, how to build Docker images, run containers, and use tools like Docker Compose for orchestration. It also discusses security best practices like running containers without root privileges and options for container orchestration at scale, such as Docker Swarm, Kubernetes, and cloud-based services from AWS, Azure and Google.
Docker is an open source platform that allows developers to package applications with dependencies into standardized units called containers that can run on any system with Docker installed. Containers isolate applications from one another and the underlying infrastructure using resource isolation provided by Linux kernel features like namespaces and cgroups. This allows developers to easily deploy and run distributed applications without having to rebuild them for each platform.
Windows Server Containers- How we hot here and architecture deep diveDocker, Inc.
Porting Docker for Windows is no small feat. The technology behind Docker today takes advantage of Linux capabilities like namespaces and cgroups. For native containers to exist on Windows and to have a Docker Engine for Windows, first similar primitives needed to be developed into the Windows operating system. In this session we will explain these Windows primitives in relation to similar primitives in Linux and other architectural changes on the OS and Engine side to make containerization possible. The process of porting includes not only the technology but also open source community interactions and cultural changes to enable this development. And of course there will be a cool demo…
This document discusses containerization and the Docker ecosystem. It provides a brief history of containerization technologies and an overview of Docker components like Docker Engine, Docker Hub, and Docker Inc. It also discusses developing with Docker through concepts like Dockerfiles, images, and Fig for running multi-container apps. More advanced topics covered include linking containers, volumes, Docker Machine for provisioning, and clustering with Swarm and Kubernetes.
This document provides an introduction to Docker. It discusses key Docker concepts like OS virtualization using containers as opposed to virtual machines. Containers isolate processes and filesystems using cgroups, namespaces and UnionFS. Namespaces provide isolation for processes, networking, mounts etc. Cgroups are used to limit, account and isolate resource usage. The document also covers Docker storage and networking as well as security best practices.
Presentation on the Linux namespaces and system calls used to provide container isolation with Docker. Presented in March 2015 at http://www.meetup.com/Docker-Phoenix/ in Tempe, Arizona.
Just as the roles of CIOs and CTOs have needed to rapidly evolve along with the pace of technology, it is now becoming critically important for lawyers to understand emerging software security challenges.
Container security involves securing containers at both the host and application level. At the host level, Linux technologies like namespaces, cgroups, SELinux, and seccomp provide isolation between containers. Container images are also scanned for vulnerabilities. The OpenShift platform provides additional security features like role-based access control, network policies, encrypted communications, and controls over privileged containers and storage. Application security best practices within containers include using HTTPS, securing secrets, and API management tools.
An introduction to contianers and Docker for PHP developersRobert McFrazier
This document provides an introduction to containers and Docker for PHP developers. It defines Linux containers and their key components like namespaces and control groups. It explains that Docker is a container technology that packages applications and dependencies into standardized units. Docker Compose is introduced as a tool to define and run multi-container applications with Docker. Vagrant is described as a way to provide a Linux Docker host and shared folders. The document concludes by noting Docker's focus on container deployment and providing references for further information.
Introduction to Containers and Docker for PHP developersRobert McFrazier
This document provides an introduction to containers and Docker for PHP developers. It defines key concepts like namespaces and control groups that enable Linux containers. Docker is described as a container technology that packages applications and dependencies into standardized units. Docker Compose is a tool for defining and running multi-container apps with Docker. Vagrant is included to supply a Docker host and enable shared folders and port forwarding. The document outlines installing Docker and Docker Compose and distinguishes between images and containers.
Containerd - core container runtime component Docker, Inc.
Docker extracted its core container runtime component called containerd and donated it to an open source community project to accelerate innovation across the ecosystem. Containerd provides the core primitives to manage containers on Linux and Windows hosts and will be fully compliant with the Open Container Initiative standard. Major container platforms like Docker will use containerd as their core runtime component to provide a "boring" infrastructure component and allow for greater cross-platform compatibility and collaboration.
Docker Security and Orchestration for DevSecOps winsSharath Kumar
Dockers have literally transformed product deployment across the software industry. It makes traditional deployments a lot easier and supplements paradigms like Virtual Machines and Hypervisors.
While Dockers make packaging and deployments relatively simple, securing them continues to be a challenge especially when faced with Docker specific security threats such as Dockerization daemon, shared kernel and other shared resources like network and the filesystem.
Securing Dockerized deployments and orchestrating them IS, and WILL remain a key challenge for several Security practitioners and DevOps engineers.
Managing Open Source software in the Docker era nexB Inc.
Heather Meeker from O'Melveny & Myers and Michael Herzog from nexB discuss the specific impact of Docker on open source software governance and compliance.
containerd summit - Deep Dive into containerdDocker, Inc.
containerd is an industry-standard core container runtime with an emphasis on simplicity, robustness and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc..
containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users.
containerd includes a daemon exposing gRPC API over a local UNIX socket. The API is a low-level one designed for higher layers to wrap and extend. It also includes a barebone CLI (ctr) designed specifically for development and debugging purpose. It uses runC to run containers according to the OCI specification. The code can be found on GitHub, and here are the contribution guidelines.
containerd is based on the Docker Engine’s core container runtime to benefit from its maturity and existing contributors.
This presentation provides an overview of the different BSD operating systems for Linux users. It discusses the key differences between BSD and Linux, such as the release engineering process, package management, and unique features of each BSD like jails, ZFS, and DTrace. The presentation recommends some books for learning more about BSD and concludes by inviting questions.
The document discusses container security, providing advantages and disadvantages of containers as well as threats. It outlines different approaches to container security including host-based methods using namespaces, control groups, and capabilities as well as container-based scanning and digital signatures. Third-party security tools are also mentioned. The document concludes with examples of using containers for microservices and network policies for protection.
The document provides a summary of developments in 2012 for several BSD operating systems, including FreeBSD, NetBSD, OpenBSD, DragonFly BSD, and PC-BSD. It discusses their release schedules and highlights of new features. It also summarizes activities of the FreeBSD and NetBSD foundations in supporting development work and events.
This document summarizes a presentation on container security given by Phil Estes. It identifies several threat vectors for containers including risks from individual containers, interactions between containers, external attacks, and application security issues. It then outlines various security tools and features in Docker like cgroups, Linux Security Modules, capabilities, seccomp, and user namespaces that can help mitigate these threats. Finally, it discusses some future directions for improving container security through more secure defaults, image signing, and network security enhancements.
This document provides an overview of Docker containers, including what they are, how they differ from virtual machines, how to build Docker images, run containers, and use tools like Docker Compose for orchestration. It also discusses security best practices like running containers without root privileges and options for container orchestration at scale, such as Docker Swarm, Kubernetes, and cloud-based services from AWS, Azure and Google.
Docker is an open source platform that allows developers to package applications with dependencies into standardized units called containers that can run on any system with Docker installed. Containers isolate applications from one another and the underlying infrastructure using resource isolation provided by Linux kernel features like namespaces and cgroups. This allows developers to easily deploy and run distributed applications without having to rebuild them for each platform.
Windows Server Containers- How we hot here and architecture deep diveDocker, Inc.
Porting Docker for Windows is no small feat. The technology behind Docker today takes advantage of Linux capabilities like namespaces and cgroups. For native containers to exist on Windows and to have a Docker Engine for Windows, first similar primitives needed to be developed into the Windows operating system. In this session we will explain these Windows primitives in relation to similar primitives in Linux and other architectural changes on the OS and Engine side to make containerization possible. The process of porting includes not only the technology but also open source community interactions and cultural changes to enable this development. And of course there will be a cool demo…
This document discusses containerization and the Docker ecosystem. It provides a brief history of containerization technologies and an overview of Docker components like Docker Engine, Docker Hub, and Docker Inc. It also discusses developing with Docker through concepts like Dockerfiles, images, and Fig for running multi-container apps. More advanced topics covered include linking containers, volumes, Docker Machine for provisioning, and clustering with Swarm and Kubernetes.
The document discusses Docker's support for multiple CPU architectures and operating systems through multi-architecture container images and orchestration. It explains how Docker images are tied to a specific OS and CPU, requiring multi-arch images to run universally. It demonstrates building and distributing multi-arch images, and how Docker Swarm and Compose support placement and constraints for multi-arch orchestration. It concludes that maintaining multi-arch images takes effort but provides portability, and that Docker EE supports orchestrating Linux, Windows, IBM Z and Power systems through one interface.
This document provides an overview of Docker and containers. It begins with a brief introduction to 12 Factor Applications methodology and then defines what Docker is, explaining that containers utilize Linux namespaces and cgroups to isolate processes. It describes the Docker software and ecosystem, including images, registries, Docker CLI, Docker Compose, building images with Dockerfile, and orchestrating with tools like Kubernetes. It concludes with a live demo and links to additional resources.
Accelerate your software development with DockerAndrey Hristov
Docker is in all the news and this talk presents you the technology and shows you how to leverage it to build your applications according to the 12 factor application model.
Faster and Easier Software Development using Docker Platformmsyukor
Faster and Easier Software Development using Docker Platform presentation for Workshop with Open Source Community 1/2019 organized by MAMPU Malaysia under project Open Source Development and Capabilities Program (OSDeC) for Public Sector in Malaysia on January 29, 2019 at Port Dickson, Negeri Sembilan, Malaysia.
This document summarizes Docker concepts and provides steps for a local Docker development setup. It introduces Docker images, containers, and registries. It then outlines requirements for development and production configurations and provides examples of setting up a Node.js/Angular frontend and Django backend using Docker images. The document concludes with notes on continuous integration and architecture options.
This document provides an overview of Docker basics including requirements, software, architecture, and concepts. It discusses traditional servers, virtual machines, and containers. Key advantages and disadvantages of each approach are listed. Docker concepts like images, containers, layers, Dockerfile, registry, and hub are defined. Common Docker commands are also outlined.
Docker 18.09 includes several new features such as remoting using SSH, improvements to BuildKit, and support for build secrets. Kubernetes has become the dominant orchestrator, though Docker Swarm is still actively developed. Windows now supports running Linux containers natively alongside Windows containers.
Docker and Microsoft - Windows Server 2016 Technical Deep DiveDocker, Inc.
This document summarizes a webinar about Docker and Windows Server 2016. It discusses how Docker is now supported on 98% of enterprise workloads, including Windows Server 2016, providing the same benefits of Docker on Linux to Windows developers and IT professionals. It outlines how Microsoft and Docker partnered to port Docker Engine to Windows, and how Docker images can now be built and run across Linux and Windows. It provides examples of using Docker with Windows Server 2016 for development/testing and migrating applications.
From VMs to Containers: Introducing Docker Containers for Linux and Windows S...Ido Flatow
This document introduces Docker containers as an alternative to virtual machines for deploying applications. It discusses how containers provide a lightweight method of virtualization compared to VMs. The key Docker concepts of images, containers, registries and Dockerfiles are explained. Examples are provided of building and running containers on both Linux and Windows. The document also outlines how Docker can be used across the development, testing and production environments and integrated with continuous integration/delivery pipelines.
[FDD 2016] Marek Śledziński - Microsoft Windows a sprawa kontenerówFuture Processing
Idea „konteneryzacji” zadomowiła się na dobre w świecie Linuxa. Ostatnie lata pokazują zmianę myślenia Microsoftu w bardzo ciekawym kierunku, tzn. do podejścia OSS i większej współpracy z innymi firmami. Nie dziwi więc, że dziura w ofercie natywnych rozwiązań w temacie kontenerów musiała zostać zapełniona. W ramach Open Container Initiative i współpracy z twórcami Dockera, Microsoft przygotował własną wersję silnika, będącego hybrydą rozwiązań z Windowsa, Hyper-V i Dockera, pozwalającego na używanie kontenerów na systemach Windows Server 2016 (Core, Nano) i Windows 10. Rozwiązania te nie są jeszcze gotowe do masowego użycia na produkcji, ale widać, że jest to droga, której Microsoft łatwo nie porzuci. Dlatego warto już dzisiaj zapoznać się z możliwościami tych rozwiązań – jak to wszystko działa, jak zacząć, co można, a z czym są jeszcze problemy.
This document provides an overview and agenda for getting started with Docker. It discusses what containers are, the difference between hypervisor and container architecture, what Docker is and its motto. It demonstrates one click deployment of a Docker image. It then covers Docker history, platform, images, infrastructure, and files. It discusses installing Docker and understanding DNX and DNU. Finally, it demonstrates running an ASP.NET 5 application in a Docker container.
Why everyone is excited about Docker (and you should too...) - Carlo Bonamic...Codemotion
In less than two years Docker went from first line of code to major Open Source project with contributions from all the big names in IT. Everyone is excited, but what's in for me - as a Dev or Ops? In short, Docker makes creating Development, Test and even Production environments an order of magnitude simpler, faster and completely portable across both local and cloud infrastructure. We will start from Docker main concepts: how to create a Linux Container from base images, run your application in it, and version your runtimes as you would with source code, and finish with a concrete example.
The document discusses Docker and how it can benefit .NET developers. It begins with an introduction of the presenter and their background. It then outlines the agenda which includes explaining what Docker is, benefits of Docker for developers, using Docker on Windows, and how Docker can be used for ASP.NET development. The document proceeds to explain key Docker concepts such as images, containers, and layers. It also discusses how Docker can provide benefits like write once deploy anywhere, agility, control, portability, and enabling continuous integration and continuous delivery workflows. Lastly it covers using Docker with .NET on Windows and tools for developing and debugging ASP.NET applications in Docker containers.
Docker for .net developer, Container, Hyper-V, Docker Tool for VS, Windows Container, Images, Layer, Docker architecture, What is Docker, Docker Engine
Not leading edge but bleeding edge experience Dockerizing Domino server and running XPages applications. Lotus Notes applications run just fine as well.
In the future IBM will make standing up Domino servers more automated. We do have a configuration step that is manual once the server starts... but it is dockerized and replicates with on prem Domino Domain.
This document discusses Docker, an open source project that automates the deployment of applications inside software containers. It begins by describing common problems in application deployment and how virtual machines address some issues but introduce overhead. It then summarizes the history and rapid growth of Docker since its launch in 2013. The rest of the document dives into technical aspects of Docker like how images and containers work, comparisons to virtual machines, security considerations, the Docker workflow, and how Docker relates to DevOps and continuous delivery practices.
Docker Barcelona Meetup - An Introduction to BuildKitArnaud Porterie
BuildKit is a new toolkit for building Docker images that addresses performance and design shortcomings of the original Docker build system. It converts build processes into an efficient, cacheable, and parallelizable intermediate format called LLB. BuildKit can be used standalone with buildkitd and buildctl or embedded in Docker. It provides significant speed improvements over the original builder, especially for incremental builds using cached layers.
Building software: the lessons from open sourceArnaud Porterie
This document summarizes Arnaud Porterie's presentation on lessons from open source for building software. Some key points include:
- Open source projects follow patterns of "wise crowds" like having a strong mission, free entry for contributors, transparency, and fair authority to scale effectively.
- These patterns can help improve closed source software development by fostering greater collective intelligence within companies.
- Applying concepts like inner source allows companies to benefit from open source practices internally by opening codebases and encouraging cross-team contributions under shared maintainers.
- A practical checklist is proposed for implementing inner source based on principles like giving all employees access to code, having documented missions and contribution processes, and enforcing consistent processes.
DockerCon US 2016 - Extending Docker With APIs, Drivers, and PluginsArnaud Porterie
Anusha Ragunathan and Arnaud Porterie present different ways to extend the Docker Engine in increasing level of effort required: through the user-facing API, through plugins, and finally through execution drivers.
DockerCon US 2016 - Scaling Open Source operationsArnaud Porterie
This document discusses scaling open source operations at Docker. It covers three main areas: the people involved in open source projects including users, contributors and maintainers; the processes for code reviews, design decisions, and managing documentation; and the tooling for measuring activity and automating processes. Maintainers play a key role in reviewing contributions and improving infrastructure. Culture is important for a healthy community. Processes aim to balance contributor experience and code quality. Metrics and automation tools like webhooks help scale projects.
The rise of Docker, and the future of computingArnaud Porterie
Arnaud Porterie discusses how Docker has changed development, continuous integration, and deployment. Docker provides standardized, universal ways to build and run code across different languages and stacks. It allows development environments and dependencies to be defined as code in Dockerfiles. Docker images can then be built, tested, and shipped once to run consistently in any environment. Docker solves common problems around repeatability, isolation, and defining applications as immutable artifacts. The talk explores ongoing areas of innovation around container runtimes, orchestration, and user experience as containers continue to grow in adoption.
Arnaud Porterie - Using Machine & Docker to develop & build DockerArnaud Porterie
Arnaud Porterie gave a presentation on using Docker and Machine to develop and build the Docker source code. He demonstrated how to use Docker Machine to provision a Linux VM on Mac, clone the Docker source repository, and build a Docker image defined by a Dockerfile in the source that provides a consistent development environment for contributors. Developing inside containers with bind mounts allows editing code on the host and rebuilding containers as needed. This approach parallelizes work by allowing multiple dev environments for branches or projects.
The document discusses the future of C++. It begins by addressing common misconceptions about C++, such as that it never evolves and requires manual memory management. It explains how C++ has continued to evolve through new standards and techniques like RAII. It acknowledges C++ is complex but discusses how its power is necessary for performance-critical applications. It argues C++ remains important where efficiency is paramount, such as on mobile devices and in cloud computing. It concludes C++ will remain valuable for optimizing applications for major constraints like processor speed and power consumption.
Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan
This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john
Analyze the growth of meme coins from mere online jokes to potential assets in the digital economy. Explore the community, culture, and utility as they elevate themselves to a new era in cryptocurrency.
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat
The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/
HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar.
Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten.
In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich
- Zugriff auf die Konsole
- Auffinden und Interpretieren von Protokolldateien
- Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS)
- Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien
- Nutzung der Client Clocking-Funktion
Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma
My talk for the Indian School of Business (ISB) Emerging Leaders Program Cohort 9. In this talk, I discussed key issues around adoption of GenAI in business - benefits, opportunities and limitations. I also discussed how my research on Theory of Cognitive Chasms helps address some of these issues
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc
Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency.
This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data.
Attendees will learn:
- Consumer awareness around data brokers and what consumers are doing to limit data collection
- How businesses assess third-party vendors and their consent management operations
- Where business preparedness needs improvement
- What these trends mean for the future of privacy governance and public trust
This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.
Andrew Marnell: Transforming Business Strategy Through Data-Driven InsightsAndrew Marnell
With expertise in data architecture, performance tracking, and revenue forecasting, Andrew Marnell plays a vital role in aligning business strategies with data insights. Andrew Marnell’s ability to lead cross-functional teams ensures businesses achieve sustainable growth and operational excellence.
Technology Trends in 2025: AI and Big Data AnalyticsInData Labs
At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including:
-Artificial Intelligence Market Overview
-Strategies for AI Adoption in 2025
-Anticipated drivers of AI adoption and transformative technologies
-Benefits of AI and Big data for your business
-Tips on how to prepare your business for innovation
-AI and data privacy: Strategies for securing data privacy in AI models, etc.
Download your free copy nowand implement the key findings to improve your business.
How Can I use the AI Hype in my Business Context?Daniel Lehner
𝙄𝙨 𝘼𝙄 𝙟𝙪𝙨𝙩 𝙝𝙮𝙥𝙚? 𝙊𝙧 𝙞𝙨 𝙞𝙩 𝙩𝙝𝙚 𝙜𝙖𝙢𝙚 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 𝙮𝙤𝙪𝙧 𝙗𝙪𝙨𝙞𝙣𝙚𝙨𝙨 𝙣𝙚𝙚𝙙𝙨?
Everyone’s talking about AI but is anyone really using it to create real value?
Most companies want to leverage AI. Few know 𝗵𝗼𝘄.
✅ What exactly should you ask to find real AI opportunities?
✅ Which AI techniques actually fit your business?
✅ Is your data even ready for AI?
If you’re not sure, you’re not alone. This is a condensed version of the slides I presented at a Linkedin webinar for Tecnovy on 28.04.2025.
Semantic Cultivators : The Critical Future Role to Enable AIartmondano
By 2026, AI agents will consume 10x more enterprise data than humans, but with none of the contextual understanding that prevents catastrophic misinterpretations.
Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB
Want to learn practical tips for designing systems that can scale efficiently without compromising speed?
Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development.
As you explore key principles of designing low-latency systems with Rust, you will learn how to:
- Create and compile a real-world app with Rust
- Connect the application to ScyllaDB (NoSQL data store)
- Negotiate tradeoffs related to data modeling and querying
- Manage and monitor the database for consistently low latencies
Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark?
At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍
Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀
#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada
Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
AI and Data Privacy in 2025: Global TrendsInData Labs
In this infographic, we explore how businesses can implement effective governance frameworks to address AI data privacy. Understanding it is crucial for developing effective strategies that ensure compliance, safeguard customer trust, and leverage AI responsibly. Equip yourself with insights that can drive informed decision-making and position your organization for success in the future of data privacy.
This infographic contains:
-AI and data privacy: Key findings
-Statistics on AI data privacy in the today’s world
-Tips on how to overcome data privacy challenges
-Benefits of AI data security investments.
Keep up-to-date on how AI is reshaping privacy standards and what this entails for both individuals and organizations.
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul
Artificial intelligence is changing how businesses operate. Companies are using AI agents to automate tasks, reduce time spent on repetitive work, and focus more on high-value activities. Noah Loul, an AI strategist and entrepreneur, has helped dozens of companies streamline their operations using smart automation. He believes AI agents aren't just tools—they're workers that take on repeatable tasks so your human team can focus on what matters. If you want to reduce time waste and increase output, AI agents are the next move.
4. Docker for Windows
4
What it is
It’s Docker as you know it
Same user experience
It’s Windows as you know it
Complete environment inside the container
It’s native containers
Contained processes run on the host system
It’s available for testing
5. Docker for Windows
5
What it’s not
It’s not virtualization
Docker for Windows will not run Linux images
It’s not a different project / code base
The existing Docker tree was ported
It’s not quite finished
Required Windows Server 2016 (currently TP3)
7. System architecture
7
Basics
Abstraction layer between Docker and kernel
execdriver -> hcsshim -> vmcompute -> ???
Internals generally not exposed
Shared kernel
Resource controls
Namespaces
8. System architecture
8
Namespaces
Silo: extension of Windows Job object
Set of processes
Resource constraints
New: set of namespaces
New namespace virtualization
Registry
Process IDs, sessions
Object namespace
File system
9. System architecture
9
Object namespace
System-level namespace, hidden from users
C:Windows maps to Global??C:Windows
Contains all device entry points
Global??C:
Registry
DeviceTcp
Added “chroot”, one namespace per container
ContainersfooGlobal??C:
ContainersbarGlobal??C:
10. System architecture
10
Filesystem
Windows applications expect NTFS semantics
Transactions, file IDs, USN journal
Building a full union FS with NTFS semantics is hard
Hybrid model
Virtual block device + NTFS partition per container
Symlinks to layers on host FS to keep block devices small
11. System architecture
11
Base image
Public Windows API delivered via DLLs, not syscalls
Highly dependent on RPC to system services
FROM scratch
Windows images must derive from Windows base image
windowsservercore – large, nearly full Win32 compatibility
nanoserver – small, fast to boot, software may need porting
Base images are delivered separately from Docker
12. System architecture
12
Hyper-V containers
New in Windows Server 2016 TP4
Docker runs on host
Launches silo in a stateless, lightweight Hyper-V VM
VM invisible to user
Appears like a process-based container
docker run --isolation=hyperv
Use SMB over VMBus to provide layers, volumes
14. Porting Docker
14
Microsoft contributions in numbers
319 pull requests
(+) 182,315 (-) 12,113
#4 contributor in terms of pull requests
#5 contributor in terms of lines of code
15. Porting Docker
15
Technical details
Go build tags
In source: // +build windows
In the filename: daemon/containers_windows.go
Go interfaces
Graph driver (~ image storage)
Execution driver
16. Porting Docker
16
Future: multi-architecture images
Example: docker pull redis
What’s my executing OS?
Not just Windows, but also ARM, …
Proposal: docker/distribution#1068
A new image manifest format to support multi-arch
20. Demo
20
A hybrid Swarm cluster
All components speak the Docker API
Docker daemon on Linux host
Docker daemon on Windows host
Swarm master (hosted on the same Linux host)
Deploying to either is just a scheduling decision
Using Swarm constraints mechanism