-
Notifications
You must be signed in to change notification settings - Fork 4
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
Reporting: container can't be build with podman #163
Comments
Thank you olea for reporting this. I don't know podman or OCI, need to learn about it. Will look at this with earnaud! Best, Yvan |
Hi ! |
Don't worry. Just wanted to explain the case for future others finding same problem. |
I want to review this issue, maybe the next week I have time for it. Probably the solution for this issue is "not assuming you are root inside the container, installing everything in the user space." |
the error message does not seem to be linked to a permission issue. I led few researches about it, and it seems to be linked to the filesystem sanity (maybe hardware). But I may be wrong .. |
I don't have a real evidence but I don't think so. This happens always and only when EDIorg components rebuild htmltools. Maybe this should be better reported and EDIorg issue tracker or the htmltools one. Anyhow, I opened this issue more as a knowledge base entry than a MetaShARK error report :) |
I have tried to build the container image in a brand new Fedora installation (Fedora 34) with Podman (version 3.4.1, latest available). The build process was sucessful "out of the box", without any errors. So I think @olea's podman installation has any problem. |
Thank you @jesmg for your feedback! Maybe this can be related to a new MetaShARK version? |
It's possible, It could be related with an update of MetaShARK/xfun library/htmltools library. But I don't know enough about the application dependencies to be sure. |
Hi:
Probably this issue is not very important for the project but I think is appropriate to report. I've been trying to build the Metashark container using podman. Probably you know Podman is a container technology compatible with OCI. Podman is designed to be used in userspace and it's expected to be 100% compatible with docker syntax and CLI. Being well integrated in my Fedora Linux it was the obvious tool to build Metashark. But found out this not work. I'm finding a problem building htmltools as a dependency of the modules EDIorg/EMLassemblyline and EDIorg/taxonomyCleanr.
This is the error log:
OTOH, the line RUN Rscript -e 'remotes::install_version("htmltools",upgrade="never", version = "0.5.1.1")' works as expected.
I've tried to diagnose what is really happening but I don't know about the R build system to deep into this. @jesmg suspects this htmltools building trouble is caused by some kind of UID mismatch Docker admits but it's OCI incompatible.
I post this just for the record.
Configuration details:
The text was updated successfully, but these errors were encountered: