SDxCentral Weekly Wrap for Feb. 15, 2019: Google's plan will include geographic and workforce expansion. Kubernetes, Docker, and containerd impacted by the runC runtime bug. Mirantis' multi-year AT&T deal is for eight-figures.
The flaw basically allows an infected container to gain control of the overarching host container and allow an attacker to execute any command.
Once you have containers in production certain security measures must be put in place to cover network filtering, container inspection, and host security.
The company's open source partner program will divert revenue to organizations or individuals that allow blockchain-based encrypted storage on personal devices.
The software-as-a-service (SaaS) platform recreates common Docker container failures across three categories: resource, network, and state.
Inadequate container security is increasingly leading to strikes related to ransomware, cryptomining, data theft, and service disruption attacks.
Acquisition rumors are nothing new for Docker, which said it has attracted more than 1 million new developers and hosted more than 1 million new applications in its Docker Hub over the past year.
The expanded management capabilities use an application management plane that can work across different cloud providers and in on-premises locations.
The company partnered with Microsoft, AWS, Pivotal, and Docker to determine how to take its low-code philosophy to containers.
Organizations are packing 50 percent more running containers per host, with a vast majority running less than one hour.
The new specification eliminates a previously required extra “hop.”
The company sees its platform as having a scale advantage over tech-focused vendors like Docker, but with more agility than larger systems integrators like IBM.
The company launched general availability of its Kubernetes-based platform that breaks from its past reliance on Docker.
The company claims its platform is the only one that can run both Swarm and Kubernetes in the same cluster.
The organization had run into challenges with different container registries implementing the protocol using different versions, which led to compatibility issues.