summaryrefslogtreecommitdiff
path: root/doc/forum/Using_propellor_for_continers_only/comment_4_9dc985b26c29b9ce21e6c75ec03f6262._comment
blob: 72d7ca83de9405a85e43b24762beb430cfd68021 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
[[!comment format=mdwn
 username="joey"
 subject="""comment 4"""
 date="2017-05-13T17:42:41Z"
 content="""
The way propellor handles running in a chroot or container is it exports
its binary and support files into the container. This way the
haskell code can run in a container, rather than being limited to
only running shell commands in the container, and without needing ghc in
the container.

It does use the hardcoded `localdir` for that.
It would certianly be possible to make it use propellor in a different
location, perhaps using `getExecutablePath`.

Since the git-annex outside the container passes command-line options to
the one running inside the container to tell it what to do, using
`mainProperties` would also not work since that does not look at
command-line options. It would need to use `defaultMain` or
`processCmdLine` and dispatch itself, or something..
"""]]