I'd +1 the mentions of security and alignment towards k8. Docker containers do not isolate the kernel, which may prove catastrophic should a malicious container gain access. The market seems to be trending back towards microVM containers (see updates from Reinvent and KubeCon for Firecracker and Knative), so I'd recommend researching that perspective.
Other than that, you may need to look at how customers would deal with private image registries, and how auth fits into the picture to not become responsible/liable for breach potential.
Thank you for your opinion!
Yeah security is the biggest concern for this type of service.
I am thinking providing private image registries as a service like Amazon ECR. And any private registries, including hub.docker.com private image, should be used in the service.
More research is needed. Thanks!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd +1 the mentions of security and alignment towards k8. Docker containers do not isolate the kernel, which may prove catastrophic should a malicious container gain access. The market seems to be trending back towards microVM containers (see updates from Reinvent and KubeCon for Firecracker and Knative), so I'd recommend researching that perspective.
Other than that, you may need to look at how customers would deal with private image registries, and how auth fits into the picture to not become responsible/liable for breach potential.
Thank you for your opinion!
Yeah security is the biggest concern for this type of service.
I am thinking providing private image registries as a service like Amazon ECR. And any private registries, including hub.docker.com private image, should be used in the service.
More research is needed. Thanks!