1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Logo design credit goes to: tubbadu
How much CLI is required? Easiest to put it in the container and give instructions to use it via docker exec -it server_container clitool [args] .
Instructions should include mount points for the DB, so it can be persisted. Providing a docker compose file is usually the best way to do that.
Thanks! Yup a docker compose is probably the way to go.
Can the cli load/save files from outside its environment? The cli "inserts" data (day an image), and also saves links locally (in user space). Can that be done? I feel the instructions via your "docker exec..." will be executed only in the docker environment, if that makes any sense?
Edit: I guess I can provide some sort of intermediate /work/ directory if nothing else.
Yeah, it runs inside the container, so that won't have access to the external filesystem's. And intermediate directory might work, but itll be a bit fiddly.
Maybe you could supply a script that does something like:
docker cp $FILE server_container:/tmp/workfile.jpg
docker exec -it cli_tool /tmp/workfile.jpg
Could do a reverse script as well for download?
Edit: you can also pipe the files to stdin of the command:
cat input.jpg | docker exec -it server_container cli_tool upload
docker exec - it server_container cli_tool download > output.jpg
Yeah I probably have to build some sort of "pass through" script if I want the cli in a docker, which sort of defies the purpose of ease of use.
Maybe a simple script (just forwarding things and copying files) would be better "tolerated" as it can be checked more easily for bad code. Or I could just "make it work" so people can have a go at it at least I guess.
Thanks again!
You can define where you want the volumes mounted so you can just have a folder where the cli utility will do it's work.
Yeah, lot's of copying and extra work for the user though.
symlinks?
Can you link from inside a docker with that?? Or do you mean setting them up on the go in the working director?
Not from inside but the volume can be placed anywhere on the filesystem. You'd define where they'd go on the docker compose. Look at a couple examples in https://www.linuxserver.io/ Great examples all around.
Thank you. Yes I know about it, will check out the link, the more info the better!
What language is the CLI written in?
Yes, running a CLI from inside a container can be a pain, but it's not a big deal for the people asking.
I would just provide a trivial Dockerfile and see if anyone uses it.
It's written in python.
Can it access files from outside its environment, are there any tricks for that?