-
Notifications
You must be signed in to change notification settings - Fork 135
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
Openmonero not build with monero v0.17.2.0 #175
Comments
Looking into this, seems (@moneroexamples I'll check this out!) |
@j-berman Thank you. |
p.3 failed for me with the same error on my first attempt, and then very strangely succeeded on my second attempt. It didn't really make sense for me to try twice, but I tried it anyway, and it worked. I'm guessing there may be some kind of caching issue going on with docker, and it's not pulling the latest from openmonero which includes my fix to #172. Try building p.3 with the --no-cache option and see if that works: |
Hi. Dockerfile is always built without a cache. |
Can you add this command after cloning openmonero?
Then share what gets output from that added command? That'll show with certainty whether or not the fix is present in |
|
Ok, was able to reproduce the error consistently in a vm, and built it successfully in the vm with this workaround:
This solution is hacky. I will look into a more concrete fix, but it should work for you in the meantime. |
I added the changes to FindRestbed.cmake proposed by @matyushkins in this branch https://github.com/moneroexamples/openmonero/tree/docker_build I tested the docker build for this branch using following
The docker build succeeds in my tests. |
@moneroexamples think I'm missing something maybe, but that branch looks like the same as master, no? |
@j-berman I see. Then its even better, since it works, so I'm confused what is the issue with the build in the docker? |
@moneroexamples his original dockerfile that points to master builds successfully locally for me too. But strangely, it failed once for me, and then succeeded on all subsequent attempts, even on attempts when I disabled the cache with --no-cache. I figured he may have some caching issue with docker, but it seems that's not the case, and it's failing for him every time he tries. So I spun up a fresh VM, and tried building the dockerfile in there, and it consistently failed to build for me in the VM too. This workaround did the trick for me in the VM, so I'm thinking it'll work for @matyushkins too, although it's not a pretty solution. I'm thinking maybe there's some kind of race condition in the build process, preventing Restbed from getting placed in the correct place during the build sometimes? That's what I was going to explore next. There's probably a simple fix in there somewhere. It's an odd issue indeed considering docker is supposed to be consistent across all machines (if it succeeds on one machine, would expect it to succeed on another). |
@j-berman Now I understand. Thanks. I will try to build few times as well and see how it goes. |
It worked. Everything is assembled and works in a stack. Thank you. |
Hey! We’re trying to collect the openmonero with monero source code v0.17.2.0 but we’re receiving errors. could you please check the following?
You can see the error we’re receiving with the above parameters (check p.3) at the very beginning of the email (check p.1). So now the openmonero source code cant be collected. What should we do?
The text was updated successfully, but these errors were encountered: