Closed olifre closed 7 years ago
This may be a duplicate of #6; does it work with absolute paths?
This may be a duplicate of #6; does it work with absolute paths?
You are right, that fixes it!
And indeed, even though that might now be a bit off-topic here:
I just now also found my mistake (which produced almost the same error message, so I thought it was the same issue) when using Singularity-built images, or docker-built images, extracted manually.
Reading through https://github.com/hpc/charliecloud/blob/master/bin/ch-tar2dir , I learnt that you need /oldroot
to exist (and place a sentinel within).
So I will now add /oldroot
to all images we are building to have them compatible both with Singularity and Charliecloud.
There's still a different problem when using CVMFS, though - I'll have a deeper look and provide more info in a separate issue once I have collected enough informaton.
Thanks! :-)
Trying with current master, I get:
The image was built following the tutorial, i.e.:
(it currently lives in my home, but I plan to build a proper package for Gentoo in the near future, maybe also for other distros)
Checking with
strace
, I see:It's bit strange to see:
in there, when the container actually lives in
ubuntu/hello
... Any ideas what could be wrong?