-
Notifications
You must be signed in to change notification settings - Fork 13
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
Decide on filesystem layout #246
Comments
'it depends'. How would you run In a multi-stage container build, you'd start with doing a Then in the next stage, you'd do Obviously, this would require the application to work in such a way, with all expected filepaths. It's fine to install into See here for an example that I did: https://github.com/tvheadend/tvheadend/blob/master/Containerfile.alpine |
@oliv3r That makes sense. The app is configured and built using CMake, so instead of using
I believe the equivalent to I already have the multi-stage build in my Dockerfile, so the changes would only be to modify the first "builder" stage to use the I will create a PR with these changes. Thank you for the input! |
Btw, here's an example I did a while ago for cmake. I probably have better ones, but my memory fails me :) https://github.com/Cisco-Talos/clamav-docker/blob/main/clamav/unstable/alpine/Dockerfile the example is a bit 'confusing' as it does a few unexpected/non-standard things, but overal, still a good example using cmake. I think https://github.com/Cisco-Talos/clamav-docker/blob/main/clamav/unstable/alpine/scripts/docker-entrypoint-unprivileged.sh is also useful for a decent, still simple, daemonized entry point for the container (which would have been my next issue report :p) |
I am not clear on the idiomatic/conventional way to lay out the directory structure for an app such as this. I suppose putting the executable in
/usr/local/bin
would be most correct?However there are two other directories required by the executable at runtime:
templates/
(where mustache templates for templated HTML endpoints created by the user are found, needs read access)designs/
(where uploaded ODB++ designs are located and then read from, needs r/w access)Currently the directory structure is thus:
I suppose the two runtime directories should be placed in
/var
somewhere?The path for the two directories can be specificed at launch via CLI args. Try
ObdDesignServer --help
or see the ENTRYPOINT key in the Dockerfile for more details.The text was updated successfully, but these errors were encountered: