dvc: error on dvc get: GLIBC_2.18 not found. installed with fedora/centos

[hadoop@hostname ~]$ dvc get \
>     "https://x-token-auth:$GITHUB_TOKEN@$MODEL_REPO_URL" \
>     experiments/prod/model.pickle \
>     -o /mnt/repo/model.pickle
ERROR: failed to get 'experiments/prod/model.pickle' from 'https://x-token-auth:REDACTEDTOKEN@github.com/WPMedia/REPOURL.git' - Failed to clone repo 'https://x-token-auth:REDACTEDTOKEN@github.com/WPMedia/REPOURL.git' to '/tmp/tmpxfz0sxdedvc-repo': Cmd('git') failed due to: exit code(128)
  cmdline: git clone --no-single-branch -v https://x-token-auth:REDACTEDTOKEN@github.com/WPMedia/REPOURL.git /tmp/tmpxfz0sxdedvc-repo
  stderr: 'Cloning into '/tmp/tmpxfz0sxdedvc-repo'...
/usr/libexec/git-core/git-remote-https: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /usr/lib/dvc/libstdc++.so.6)
'

Please provide information about your setup DVC version(i.e. dvc --version), Platform and method of installation (pip, homebrew, pkg Mac, exe (Windows), DEB(Linux), RPM(Linux))

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 21 (17 by maintainers)

Commits related to this issue

Most upvoted comments

Thanks!!

@AlJohri Patch is merged to master, I was unable to reproduce the error after patch. A new release should be available soon.

@AlJohri another patch on the way.

To put some context for future: We used fix_env to delete LD_LIBRARY_PATH from env if it was empty before Pyinstaller did its magic.

The problem is that gitpython did not “use” provided env, but used it to update its own git.cmd._environment. If there was no “LD_LIBRARY_PATH” in provided env, its value has not been updated.

So in theory fix env["LD_LIBRARY_PATH"]=None should work. Surprisingly it did not, thought env["LD_LIBRARY_PATH"]="" did.

Need to investigate why the first version does not work, might be another bug on our site, or something wrong with gitpython.

I was able to reproduce the problem on vanilla EMR cluster machine.

@AlJohri I am trying to reproduce the problem using docker and aws instance, and I am unable to, could you ssh to your instance and check what linux is it running? something like cat /etc/os-release

Sorry, other stuff got in the way. Will try to get back to this ASAP.

@AlJohri Got it. I’ll also try to reproduce in the morning with some older docker image. 🙂

I’m not sure if I was using the latest version (I’ll check soon) but I definitely installed it on a fresh cluster so I got whatever version https://dvc.org/rpm/dvc.repo defines.