warning libmamba linux version not found (virtual package skipped) #227
Comments
|
Hello @thib12 - thank you for your interest in micromamba. Can you please supply me some more information to help me reproduce the issue. You are seeing the warning when building an image with the given Dockerfile, or does the warning occur when you are running a command within a container? The complete set of commands used to produce the error would be helpful. |
|
Hello, thanks for your answer ! |
|
I'm not seeing this message when I build on my mac. Can you please run the following 3 commands and post the output? uname -a
docker --version
env |
Thanks ! |
|
It appears this is being caused by your kernel version not matching a regex. There was commit to fix this problem back in August, but it did not cover your corner case. What linux distribution are you running? |
|
OK I see. I run CentOS Stream release 9. |
|
After you build your image, could you run the image and get the output from |
|
Sure, |
|
Can you try |
|
If I run |
|
I was wrong about the regex being the problem. I still have not been able to reproduce this, which makes troubleshooting hard. Inside your image, can you please run uname -r
echo $?and report back the output? Thanks! |
|
Hello, For the given Dockerfile: This is what I get |
|
I have a very similar issue with RockyLinux 9 |
|
Same issue on RockyLinux 9.1, any updates on the problem? |
|
I have not been able to reproduce this. I ran a Rocky 9.1 VM on my x86 mac using virtual box and did not see the reported error messages. I don't have any bare metal available to directly install Rocky Linux on. On a system that is producing these error messages, I'd be interested in seeing the output from: strace -f -e trace=%process micromamba info --log-level=1 Be warned, that command may take a couple of minutes to return. |
|
Sure, @wholtz For the given Dockerfile: The output is |
|
`Step 6/8 : RUN strace -f -e trace=%process micromamba info --log-level=1 debug libmamba Loading configuration populated config files : |
|
Just popping in to say that I have this same issue with |
|
@meridionaljet (or anyone else who is hitting this problem) - can you please:
|
|
|
Thanks @meridionaljet! I was hoping this was going to be a general |
|
Facing this problem as well. Using WSL with I'm not sure if it's related but trying to install Could anyone else facing this try installing |
|
Seeing this still: Host os is ok: In docker not: |
|
I also had this problem on a Manjaro machine, but then I followed the instructions in this comment in issue #267 and now things are working for me. The issue was specifically about pip, but maybe it will also help someone else. |
|
Thanks for the intriguing report @pabloabur. It will be interesting to see if anyone else on this issue has success with the |
|
In my case, setting In the current build I am working on, I have the following inside the container:
using the mambaorg/micromamba base image |
|
@wholtz I was running into the same issue. I had no issues installing my env with micromamba outside of a container, but was running into the same warning inside one. I am on arch linux, which seems to be to same systems having issues in @pabloabur comment link. With that flag, it seems to work fine inside of the container. |
|
I also tested the same solution on Ubuntu WSL under Windows 11, and it worked. |
|
I was hoping that building an image with an artificially low I still want to find a reproducible way of causing this error..... |
With the given dockerfile
I get the following warning:
This warning appears whatever the package I try to install.
The text was updated successfully, but these errors were encountered: