When storing docker images in a file system, I want to know if I can intentionally fragment the file into an Overlay2 structure and save it separately in each layer, so I'm trying to run various docker images as containers.
However, it's not easy to see this because you don't know the actual scenario of the container environment (I'm not sure where docker images contain source code or program files). So I have two questions.
First of all, when I save the docker image in the file system, can I intentionally fragment the file into the structure of overlay2 and divide it into each layer and save it?
If possible, how can I check this? (Check overlay2 directory or diff directory)
In addition, in general situations, when operating a service configured in a docker container environment, which directory should I check to learn in detail how the source code, programs, and executables of the image are stored on the layer? (I want to check it with my own eyes.)
I studied Docker and UFS and learned that image layers were created when building Docker files.
However, we could only verify that the directory on each layer was chained in the var/lib/docker/overlay2 directory or the directory named SHA256 and could not visually determine which directory the source code or program was stored in.
Thank you!