Updating dockershim FAQ with Mirantis announcement
Signed-off-by: Brandon Mitchell <git@bmitch.net>
This commit is contained in:
@@ -47,6 +47,15 @@ and other ecosystem groups to ensure a smooth transition and will evaluate thing
|
|||||||
as the situation evolves.
|
as the situation evolves.
|
||||||
|
|
||||||
|
|
||||||
|
### Can I still use dockershim after it is removed from Kubernetes?
|
||||||
|
|
||||||
|
Update:
|
||||||
|
[Mirantis and Docker have committed to maintaining the dockershim][mirantis] after
|
||||||
|
it is removed from Kubernetes.
|
||||||
|
|
||||||
|
[mirantis]: https://www.mirantis.com/blog/mirantis-to-take-over-support-of-kubernetes-dockershim-2/
|
||||||
|
|
||||||
|
|
||||||
### Will my existing Docker images still work?
|
### Will my existing Docker images still work?
|
||||||
|
|
||||||
Yes, the images produced from `docker build` will work with all CRI implementations.
|
Yes, the images produced from `docker build` will work with all CRI implementations.
|
||||||
|
|||||||
Reference in New Issue
Block a user