Open byteshiva opened 5 years ago
This is an interesting use case... Thank you for opening the ticket @byteshiva ! I assume this is the Dockerfile for the image you are trying to minify: https://gitlab.com/BuildStream/buildstream-docker-images/blob/master/buildstream/latest.Dockerfile . I also assume you want the tools explicitly installed in that Dockerfile to stay there, so you can use them later. Can you share an example (or two :-)) of how you use the BuildStream image? Trying to understand how to support this use case...
The failure itself is a bit strange... It complains about a permission problem with the files docker-slim
copied from the temporary container it created internally. The latest version of docker-slim
shouldn't have the same permission problem because it archives the container artifacts before they are copied from the target container, so the docker-slim
master app doesn't need to worry about the permissions set on the files that were copied.
This is an interesting use case... Thank you for opening the ticket @byteshiva ! I assume this is the Dockerfile for the image you are trying to minify: https://gitlab.com/BuildStream/buildstream-docker-images/blob/master/buildstream/latest.Dockerfile . I also assume you want the tools explicitly installed in that Dockerfile to stay there, so you can use them later. Can you share an example (or two :-)) of how you use the BuildStream image? Trying to understand how to support this use case...
The failure itself is a bit strange... It complains about a permission problem with the files
docker-slim
copied from the temporary container it created internally. The latest version ofdocker-slim
shouldn't have the same permission problem because it archives the container artifacts before they are copied from the target container, so thedocker-slim
master app doesn't need to worry about the permissions set on the files that were copied.
To start with, I'd like to create a disposable dev/sandbox environment along with buildstream to deliver different packages right from flatpak to go executables. Based on the meta data the dev Container profile changes. Why to choose docker-slim, for the obvious reason to lower the size of dockers.
There is another usecase where I would like to create a disposable go dev server to capitalize some of the language server protocol features. In this usecase I would have very low end machine for development all the heavy lifting code analysis and build and others would be done on the remote server. It could be related with cloud IDEs.
Let me test it with latest docker-slim and will update with it's state of error.
I'm getting below error while compressing buildstream/buildstream image,. Can someone tell me if I'm missing something here.