What is the `coreutils` package used for inside of...
# tools
p
What is the
coreutils
package used for inside of nf-core? I just ran into a nasty bug where I was using a conda environment containing nf-core, wrapped in a container by hpc-container-wrapper/tykky because it was being used on a HPC system with a limited # file quota, and was surprised to see many of my regular bash calls were taking ages to complete (i.e. a job script was taking much longer than expected because it contained a lot of find/loop/basename parsing steps, and on the cli every command had a few seconds of delay before and after, and I was ready to mail our hpc team to help me debug a latency issue).
p
I don't see it listed in the code base (beyond some strings in tests) so I guess it's a second level dependency
s
I’ve had a similar issue where certain Unix utilities provided in the base BioContainers image can run slower than those on a standard Unix system. The cause of this in my case was use of the BusyBox grep from the base BioContainers image rather than the more common / standard coreutils grep. After installing coreutils grep into the image the slow down was resolved (relevant PR here)
👍 1
p
Hi both! It seems to be an nf-test dependency (as well as a nextflow one):
Copy code
$ grep "coreutils" */info/index.json
coreutils-8.25-1/info/index.json:  "name": "coreutils",
nextflow-24.10.6-h2a3209d_0/info/index.json:    "coreutils",
nf-test-0.9.2-h2a3209d_0/info/index.json:    "coreutils",
Good to know about the BusyBox thing too, but in this particular case the issue seems to have been overhead with spinning up containers for every call to e.g.,
ls
, instead of using the system ones, because they were pulled in via coreutils as part of the containerized conda environment (which was pre-pended to my PATH).