Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

A completely closed source docker container

I was wondering if it is possible to offer Docker images, but not allow any access to the internals of the built containers. Basically, the user of the container images can use the services they provide, but can't dig into any of the code within the containers.
Call it a way to obfuscate the source code, but also offer a service (the software) to someone on the basis of the container, instead of offering the software itself. Something like "Container as a Service", but with the main advantage that the developer can use these container(s) for local development too, but with no access to the underlying code within the containers.

My first thinking is, the controller of the Docker instances controls everything down to root access. So no, it isn't possible. But, I am new to Docker and am not aware of all of its possibilities.

Is this idea in any way possible?

like image 730
m8a Avatar asked May 06 '16 05:05

m8a


People also ask

Is docker closed source?

3) No changes for Linux/open source users As Bret explains, Docker Desktop is a mix of open source and closed source software, and it's the closed source bits to which the Docker Desktop licensing changes apply.

Are docker containers open source?

Docker is an open source containerization platform. It enables developers to package applications into containers—standardized executable components combining application source code with the operating system (OS) libraries and dependencies required to run that code in any environment.

What is a Dockerized container?

Dockerizing is the process of packing, deploying, and running applications using Docker containers. Docker is an open source tool that ships your application with all the necessary functionalities as one package.


1 Answers

An obfuscation-based only solution would not be enough, as "Encrypted and secure docker containers" details.

You would need full control of the host your containers are running in order to prevent any "poking". And that is not the case in your scenario, where a developer does have access to the host (ie his/her local development machine) where said container would run.

like image 180
VonC Avatar answered Oct 07 '22 05:10

VonC