The C++/Makefile SDK container is running as root. This means that any files generated by the build process will be owned by root in the host system filesystem. Specifically, I am testing rpcgen based applications and after generating the .c and .h files, they are owned by root and I cannot easily manipulate them.
My workaround is to add "USER 1000" just before the WORKDIR statement of Dockerfile.sdk. That works but is hard coded to a user ID of 1000. Ideally we would have a better way to handle this that automatically determined the UID or at least was more easily user configurable.
I assume any other templates that run builds inside containers will have similar issues.
The C++/Makefile SDK container is running as root. This means that any files generated by the build process will be owned by root in the host system filesystem. Specifically, I am testing rpcgen based applications and after generating the .c and .h files, they are owned by root and I cannot easily manipulate them.
My workaround is to add "USER 1000" just before the WORKDIR statement of Dockerfile.sdk. That works but is hard coded to a user ID of 1000. Ideally we would have a better way to handle this that automatically determined the UID or at least was more easily user configurable.
I assume any other templates that run builds inside containers will have similar issues.