-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
Local docker image fails to build #1243
Comments
What is the architecture? Could you send output of |
AMD64
Sure:
|
Got amd64 pc and still builds with no problem on my machine. Could you send me the logs from previous step #12? also since i can't duplicate the problem could you edit the Dockerfile and split one RUN
into multiple ones to see which fails?(probably will be the last one)
also in previous step: (in Dockerfile)
add debug print of files in
I suspect that |
@mksdev i edited the Dockerfile as you suggested and tried to build:
|
From the log it seems that everything went well, binaries are built but only problem will be the Still can't duplicate the problem on my machines, I have tried to build the docker image on multiple amd64 and arm64 machines and there is no problem with |
Might be problem with machine you are building the image on or some docker internal configuration. Could you try the build on different system? |
I tried. No difference.
Docker should work independently from my local environment and i haven't touched docker's internal configuration. This is an odd issue.
I could set up an ubuntu vm and test there, but it will take time and might be a bit overkill. |
If i remove the |
Idea behind the command is to restore folder structure of shared libraries matching the original one. Without The actual files in /tmp/ldd with the same folder structure (see the logs) are
which are contained in build step image Based on https://unix.stackexchange.com/questions/288774/what-is-the-added-value-of-the-t-option-in-gnu-cp-and-mv try to change it to
i'll make pull request if it works,
My guess is that underlying filesystem or whatever docker is using during the build process could have problem with what |
Sadly, it didn't work. I don't know where to go from here, i'm unable to run Firo in any way on my Fedora system. |
What is your current version of Fedora and installed version of docker? From docker documentation it seems that error is actually 128 + signal number of original process, so 135 would be signal 7 -> SIGBUS. To debug it more you need to run strace on First debug the host:
send me the log file Second debug the cp command:
run with
send me the log file |
Thanks for looking into this @mksdev :)
Fedora 37, Docker version 24.0.2, build cb74dfc I sent you email with the logs. |
not sure if you see my email on github, but if not you can send them to |
Turns out i sent the email to the wrong person :) Sent now. |
Based on the logs it fails after start of copy change command to
|
It did! Thanks. We can mark as resolved after the change is in. Should i pr it? |
PR here #1251, thanks for the report. I am using same build process on my other c++ projects, I will use this fix in more places. |
Fixed in #1251 |
I'm trying to build the Dockerfile in this repostiroy, but the process fails:
The text was updated successfully, but these errors were encountered: