Skip to content
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

LD_LIBRARY_PATH is modified when running Docker, causing issues #781

Closed
polm opened this issue Nov 2, 2020 · 5 comments
Closed

LD_LIBRARY_PATH is modified when running Docker, causing issues #781

polm opened this issue Nov 2, 2020 · 5 comments
Labels
bug Something isn't working

Comments

@polm
Copy link

polm commented Nov 2, 2020

Sorry but I'm not sure this is the right repo to file this against. If there's a better repo let me know.

Describe the bug

A Docker container run via Github Actions has the LD_LIBRARY_PATH modified and that causes issues. For example, cloning a git repo with an https url causes libcurl related errors.

To Reproduce

Git clone with an https url in a Docker container run from a Github Action.

Expected behavior

I expect LD_LIBRARY_PATH to not be modified, or for that to be explained somewhere, but I haven't been able to find it.

Runner Version and Platform

Version of your runner? It's hosted on Github Actions, not sure.

OS of the machine running the runner? Linux

What's not working?

Git clone for https urls doesn't work, exits with error.

Job Log Output

/usr/local/libexec/git-core/git-remote-https: error while loading shared libraries: libcurl.so.4: cannot open shared object file: No such file or directory

https://github.com/polm/fugashi/runs/1291141895?check_suite_focus=true

@polm polm added the bug Something isn't working label Nov 2, 2020
@polm
Copy link
Author

polm commented Nov 2, 2020

Oh, for more details please see this issue, where this was discovered.

pypa/manylinux#812

@TingluoHuang
Copy link
Member

@polm
Copy link
Author

polm commented Nov 3, 2020

Thanks, I will follow up there.

@polm
Copy link
Author

polm commented Nov 11, 2020

I checked with actions/setup-python and someone on that project says the issue is not with the setting of environment variables, but with the env vars being passed from the outer environment into the Docker container.

pypa/manylinux#812 (comment)

It does seem odd that env vars would automatically go to the Docker container. Can you shed any light on that behavior?

@polm polm reopened this Nov 11, 2020
fantix added a commit to fantix/immutables that referenced this issue Feb 10, 2021
Refs actions/runner#781, add LD_LIBRARY_PATH manually here for now
before an upstream fix is added.
fantix added a commit to MagicStack/immutables that referenced this issue Feb 10, 2021
Refs actions/runner#781, add LD_LIBRARY_PATH manually here for now
before an upstream fix is added.
fantix added a commit to MagicStack/uvloop that referenced this issue Feb 10, 2021
Refs actions/runner#781, add LD_LIBRARY_PATH manually here for now
before an upstream fix is added.
fantix added a commit to MagicStack/uvloop that referenced this issue Feb 10, 2021
Refs actions/runner#781, add LD_LIBRARY_PATH manually here for now
before an upstream fix is added.
@TingluoHuang
Copy link
Member

I am going to close this since the root cause is actions/setup-python#159

Olaf1022 added a commit to Olaf1022/Ultra-fast-asyncio that referenced this issue Aug 13, 2023
Refs actions/runner#781, add LD_LIBRARY_PATH manually here for now
before an upstream fix is added.
tomkinsc added a commit to broadinstitute/viral-phylo that referenced this issue Mar 20, 2024
disallow actions/setup-python from changing environment variables; see:
actions/runner#781
actions/setup-python#411
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants