question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using softlinks for pointers to libraries

See original GitHub issue

Created from discussion topic https://github.com/elyra-ai/elyra/discussions/1646 at request of @lresende

I’d like to have a directory setup something similar to the following:

root
  -- common_libs
  -- pipe_1
     -- pipe1_files
     -- softlink_to_../common_libs
  -- pipe_2 
     -- pipe2_files
     -- softlink_to_../common_libs

The idea is that there is just one common_libs directory containing all my common libraries, and each pipeline dir contains a soflink to that directory. That way, I can easily import the common libs into the stages of my pipeline.

The problem arises when I try to run the pipeline on kubeflow - the stages fail when trying to import anything from common_libs because it cannot find the file.

It appears the tar command used to create the archive for the pipeline stages includes the softlink to common_libs rather than the files themselves. This is the default behaviour of tar but I believe it can be changed by using the --dereference flag - which includes a copy of the file in the archive rather than the link.

Any chance of changing the tar command for building the stage archives to include the dereference flag ?

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
simon-streamotioncommented, May 10, 2021

Let me check with my org re. contributions to open source code 😃

0reactions
ptitzlercommented, May 7, 2021

@simon-streamotion would you be interested in delivering the change in a pull request?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Using softlinks for pointers to libraries #1646 - GitHub
Using softlinks for pointers to libraries. ... The idea is that there is just one common_libs directory containing all my common libraries, ...
Read more >
Symbolic Links (The GNU C Library)
GNU systems support soft links or symbolic links. This is a kind of “file” that is essentially a pointer to another file name....
Read more >
symlinks and .so files on linux - what you need to know
Everything you need to know about symlinks and .so files on Linux. ... Using the library from The Experts #. You've bought the...
Read more >
Soft and Hard links in Unix/Linux - GeeksforGeeks
Links allow more than one file name to refer to the same file, elsewhere. There are two types of links : Soft Link...
Read more >
c++ - Why so many symbolic links? - Stack Overflow
My question is, since it already put the real shared library libopencv_core.so.2.4.9 in /usr/lcoal/lib, why bother to create a symbolic link ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found