-
Notifications
You must be signed in to change notification settings - Fork 626
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
Docker builds with uid/gid 0 (root) #968
Comments
If you already have a fix feel free to send a PR. |
From the README it says bumping to These 2 builds are the only ones that are unhappy. EDIT: Unsure what to do other than to build and use a different image. |
@michael-o knows about freebsd much more than I do, and may advise on supporting only v11+. It seems the empterdose image has been updated and supports aarch64 now, which would allow to drop my own fork. |
Those should be installable with sudo, even when running the container with an unprivileged user, no? |
@gotson Let me try to understand the issue and how I can help here. |
First of all note:
I'd first update and then retry and see results. 9.3 is very old now (2016-12-31). |
@05nelsonm are you able to clarify why the original issue of having directories / files owned by root is a problem? It's been like this for some time, and never has been a problem for anyone. Is that because your build system differs in some ways? We even build all native libs on github actions without any issues. |
Yes I am building on laptop from non-root user ( Have everything building now with the proper
Yes the container for GH actions is fine b/c it's In general, running docker as root is ill-advised.
Looking into it now |
Briefly looking at the issue and the output (don't attach screenshots, they are horrible) it does not specificly apply to FreeBSD, but on how the actual container is run. I still would try to upgrade to 11.4 first and see if the error exist. Doesn't make sense to analyse an old image's behavior, no? |
Yes I've tried updating to new version and adding |
What is the exact output? I bet that the source user does not exist in the container, how can it? |
The |
So it is not a suitable replacement for the old one at the moment or you need a layer on top with OpenJDK 8? |
Here's the output from upgrading to with uid:gid
with out uid:gid
EDIT: Yes I think a layer on top with |
Let's start without uid first: |
I don't quite understand how root on your laptop could not have the permissions to write to your own user folder. |
It's the base files for linux x86_64. Docker builds them and outputs with root user to |
Not 100% certain on what those variables in |
Installed a AL8 VM here and trying this myself. Needs a bit of time. |
K. My commit for adding a user to other builds is 05nelsonm@56b45e3 |
Got the OP semi-resolved on It does not work though if the
|
@05nelsonm what's your local setup ? I am myself running this locally on a mac, and i have no problem. My mac user is not root. |
Yeah mac is a little different than linux.
Cloned the repository into my project's directory and ran |
So, with the exception of
Would it be advisable to submit a PR and then handle the freebsd complications at a later date in time? |
I cannot properly link with the 11.4 image because of:
The prefixes strip command is missing. |
See also: MrDOS/freebsd-cross-build#1 (comment) |
Describe the bug
When building native binaries via
make native-all
, output directories in/target
have root user permissions (uid 0, gid 0) resulting in build errorPermission denied
To Reproduce
make native-all
Expected behavior
building via dockcross should utilize the user id and group id from the shell of the user executing it such that their output matches that of the user.
e.g.
Logs
Environment (please complete the following information):
x86_64
3.43.0.0
Additional context
The text was updated successfully, but these errors were encountered: