-
Notifications
You must be signed in to change notification settings - Fork 43
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
Improve Docker container #385
Comments
Thanks! We will take this into account |
You now need to run |
@artur-sannikov is this ready? |
@antagomir, currently the most up-to-date container is on
Image |
@artur-sannikov MOFA2 is causing this issue, but any idea why? Any idea how to fix this? |
I'm not even able to build an image on GitHub: https://github.com/artur-sannikov/OMA/actions/runs/10055341285/job/27791808192 because it fails due to API rate limiting (it's too big, I guess). I want to try standalone Docker build without relying on BiocBook. |
The #585 is merged now. Can we close this one as well @artur-sannikov ? |
@antagomir, the image |
If you can take care of closing this issue when it is ready that would be great. |
Someone with access to the container registry settings, needs to make the image public. |
That requires changing settings from organization level. Does it now work? Another thing: It seems that Docker is not working anymore since it exceeds the cache. I tried to fix it month ago (62d6764, d824b65, 80a8541, 4e80d2f, 988a78c). It worked, but now it exceeds the limit again (Maybe new packages were added to OMA). See the GHA report: https://github.com/microbiome/OMA/actions/runs/10271529523/job/28421702599 Would you be able to fix this @artur-sannikov ? This is somewhat urgent since the run does not work and OMA is not updated. I would recommend involving BiocBook to this. This affects all BiocBook users and the guy might have some idea how to fix. |
We can probably afford extra space when necessary but it would be anyway good to minimize the loads. |
It took > 1 hour to build: https://github.com/artur-sannikov/OMA/actions/runs/10280588960/job/28448241727#step:12:8806, but the building part was successful. It was not pushed due to token permissions I think, but it's not a problem. I think such long build time is due to miniconda installation to fix #585. I cannot build the image locally because I hit the API rate limit. |
Ok, so at the moment, the Docker container builds and is published on the package page. However, the current version
|
Right now Docker container is very basic and cannot be used.
I managed to run in with Podman 4.8.3 :
It's then accessible on localhost:8787. Username
root
and password is given in shell.There are no accessible files in RStudio web-interface. Inside the container there is a
OMA_0.98.16.tar.gz
archive.BiocBook supports containerization, so it a Docker image might be nice to have because it can help avoid all dependency issues on different platforms and their versions people run.
The text was updated successfully, but these errors were encountered: