-
Notifications
You must be signed in to change notification settings - Fork 96
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
Automatically detect .so
needed
#439
Comments
I definitely don't like special syntax for rules. Think there should be separate command for that task. |
I don't get it. What do you propose? "Option 2" from above? I don't see how to make sane semantics for the command. |
Yes, I propose "Option 2": - !LddCopy
path: /dist
binaries:
- /usr/bin/swindon Should copy Possibly we could make configuration more detailed: - !LddCopy
lib_path: /dist
binaries:
-
source: target/release/swindon
path: /dist/bin/swindon |
I think |
Okay, added few options. It looks like |
Motivation
We want to build minimal containers. Currently, to make a minimal container for dynamically linked executable, we need config like this:
There are basically two things here:
ldd
Option 1
rules
option for build, like forCopy
andDepends
Or:
Pros:
Depends
,Copy
andBuild
Cons:
rules
Copy
andDepends
Option 2a
(by @anti-social )
This is meant to copy swindon and it's dependencies into
/dist
folder, so that!Build
command picks it up in the subcontainer.Pros:
!Build
commandnss
Cons:
LddCopy
andBuild
)Option 2b
Pros:
nss
are okCons:
binaries: [ /bin/bash ]
) it unclear if binary is from currently building container or the dependencyOption 3
Pros:
Cons:
!Build
stepsNotes
It looks like possible to use
elf
crate orstatic-ldd
to find out dependenciesAnother motivating implementation by oracle.
Additionally, it's a good idea to make tutorials for common setup with rust, go as major use cases and evaluate scripting languages too.
/cc @anti-social
The text was updated successfully, but these errors were encountered: