Dmitrii Kuvaiskii
Dmitrii Kuvaiskii
Have you tried to enter this GSC-generated Docker image and take a look around? With a command like: ``` docker run -it --entrypoint /bin/bash gsc-icr.io/data-security-broker/dsb-shield-postgresql-v1:v1 ``` When you enter the...
And it's not empty in the original app Docker image? Are you sure? How is this possible...
But you performed `docker exec -it 17e6f3692053`, i.e., you connected to an already-existing Docker container. Could it be that in this container, you or some script created the `/opt/` contents?...
This makes no sense to me... Could you: 1. Remove all Docker images, containers, etc. -- basically prune all Docker artifacts 2. Remove the `build/` directory in GSC -- prune...
I do not see anything special about your original Docker image. Would it be possible to reproduce the same on a clean environment (with all previously built Docker images purged)?...
> `RUN chmod 1777 /tmp` Do you know why you're doing this in your Docker image build?
@vicshi06 Can you check if PR https://github.com/gramineproject/gsc/pull/194 fixes your issue?
It feels like the USER in the original Docker image is empty or corrupted? Why do we see lines like `Step 21/30 : USER :`... Can you perform `docker inspect...
1. Would it be possible to run this application **without GSC** (without Docker, just plain binaries)? It will be easier to analyze/debug it. 2. If you want to run it...
There is some hodge-podge with UID and GID in your Dockerfile and the `bonnie` application itself. To be honest, I don't understand what's the deal with setting UID and GID...