-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add observable-builder user and use /project #10
Conversation
Adds an observable-builder user with a home directory of /project. This uses 8000 as the uid since that's not likely to collide with any users on the container runtime host machines.
Working on fixing the breakages. I just have to order the creation of the user correctly |
* Use a traditional /home directory * Combine poetry into python layer * Rename mounts * Removed unused imports * Put tar-fs into devDependencies
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. I'd like to take some time to test this manually a bit before we release it, but I don't think I'd be able to do that before Monday. Lets go ahead and merge this and I'll handle a new release next week.
@jessedearing unfortunately it looks like this would break cloud builds, at least in my local testing. The files the builder copies into the image are owned by uid 1000. Do you think we can fix this quickly, or should we roll this bac until we can figure out a way to make it compatible? |
We can change the uid to 1000 which should work. Will follow up with another PR |
I think it might have just been 1000 because that is my UID. I don't know what UID the builder will be using. I think maybe the right choice would be to have the builder explicitly specify a UID when copying files. Either way we should make sure to test this in-site in the next PR. |
Adds an observable-builder user with a home directory of /project. This uses 8000 as the uid since that's not likely to collide with any users on the container runtime host machines.
This PR also changes the tests to use a directory copy instead of a bind mount because of something with the way GitHub actions and SELinux works. Copying the files into the container before starting it will set the file system permissions correctly. A bind mount works just fine on my load build and test so it seems like an exclusive issue to GHA.