github.com/containerd/containerd@v22.0.0-20200918172823-438c87b8e050+incompatible/reports/2017-06-09.md (about) 1 # Development Report for June 09, 2017 2 3 ## Docker Schema 1 Pull 4 5 We added support for pulling Docker images which use the schema1 manifest 6 format in the containerd client. This allows pulling images from older 7 registries as well as images pushed from older versions of Docker. With this 8 change any image from the Docker Hub or registry supporting the v2 API can be 9 pulled. As part of our commitment to support OCI images, the schema 1 images 10 pulled by the client are converted to OCI images before being stored by 11 containerd. The containerd client will only support pushing these images as 12 OCI. 13 14 [#968 Schema 1 pull](https://github.com/containerd/containerd/pull/968) 15 16 ## Namespaces for multitenancy 17 18 One of the goals of containerd is to support multiple consumers. The ability to have swarm, docker, kube, and more all running on the same system and using the same containerd without having naming and actions conflict with one another. We have the namespace API merged in and most of the underlying components updated to support namespaces. You can view the namespace PR below for more information on the functionality of namespaces. 19 20 [namespaces](https://github.com/containerd/containerd/pull/963) 21 22 ## Client Updates 23 24 We added updates to the client to support attach, checkpoint and restore, exec of additional processes, and fixes. We also ported over the `ctr` and `dist` tools to use the client this week. 25 26 [exec](https://github.com/containerd/containerd/pull/940) 27 [tty](https://github.com/containerd/containerd/pull/948) 28 [checkpoint](https://github.com/containerd/containerd/pull/958) 29 [attach](https://github.com/containerd/containerd/pull/976) 30 31 # What's Next? 32 33 We only have a few features left to implement, such as [events](https://github.com/containerd/containerd/pull/956), for our 1.0 release. The rest of the month we are working on usability, bug fixes, and stability. 34 35 We will be helping out with integrations of containerd into other platforms to make sure that everyone has the functionality that they need. If you run into any problems please open an issue on github. Also Pull Requests for the problems you are having are welcome. If you have any question or help working on a change, stop by the #containerd slack channel as everyone is friendly and helpful.