[Editor’s note] As container technology became popular, Oracle began to apply container technology in cloud services. While preparing applications, Oracle also developed related tools to facilitate the construction and maintenance of containers. We are happy to announce that several tools developed by Oracle are now open source and we hope they will help you. The Smith, Crashcart, and Railcar tools are available on the Oracle GitHub page.
【 3 days to burn brain type container storage network camp | shenzhen station “this training with container storage and network as the theme, including: Docker Plugin, Docker Storage driver, Docker Volume Pulgin, Kubernetes Storage mechanism, container network implementation principle and model, Docker network implementation, network plug-in, Calico, Contiv Netplugin, open source enterprise-level mirror warehouse Harbor principle and implementation.
Smith — Secure microcontainer builder
The traditional container building process requires a series of complex steps. Smith is a microcontainer build tool that addresses build consistency and security issues. It is easy to build microcontainers from RPMS, YUM libraries, and even existing containers. See the Microcontainer Manifesto for more information on building microcontainers.
Crashcart – Microcontainer debugging tool
Thin provisioning of application containers in the production environment leads to the loss of diagnostic tools, which poses a huge challenge to O&M. While most of the diagnostics can be done on the master node, sometimes you need to do the diagnostics on file systems that are accessible to the container node. Crashcart is an application in this scenario, which loads a set of data for the running container to locate the cause of the failure. For details about how crashCart locates single-side loading data faults, see Hardcore Container Debugging.
Railcar – Optional container Runtime
Go is not necessarily the best choice for container Runtime. Note: Runtime is a component isolated by namespace and cGroups. Go is still a very smart choice for container mirroring and CLIS. Linux Namespaces And Go Don’t Mix. Part of the code for Runc (Runc is the default component of OCI Runtime) is written in C and called before the Go runtime tense starts. While Go is a great language, there are better options for smaller components that require light thread control and lots of system calls. The Rust language provides lightweight control similar to C, but is memory safe and avoids class bugs and vulnerabilities. For more information about Railcar development, see Building a Container Runtime in Rust.
Original link:Three New Open Source Container Utilities(Chilly)