Skip to content
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

Documentation #40

Open
bhagujava opened this issue May 30, 2019 · 1 comment
Open

Documentation #40

bhagujava opened this issue May 30, 2019 · 1 comment

Comments

@bhagujava
Copy link

Hi, It would be more use full with documentation

@karl-tpio
Copy link

karl-tpio commented Dec 9, 2019

Agreed. It took a while to figure out what was going on and how this image differs from the official Dockerfile. The entry point is hard coded and does not seem to like it when you specify the --config . flag manually.

here's a short version of how to use this image:

$ podman run -it --rm --volume=/etc/curator/jobs/my-job-config.yml:/.curator/curator.yml --volume=/etc/curator/jobs/my-job.yml:/actions.yml bobrik/curator:latest "/actions.yml"


{"@timestamp": "2019-12-09T21:13:49.702Z", "function": "run", "linenum": 148, "loglevel": "INFO", "message": "Preparing Action ID: 1, \"snapshot\"", "name": "curator.cli"}
...  etc

Once i stopped trying to set the --config flag manually (was being told Error: no such option: --config /curator.yml) and just used the path that the image expects:/.curator/curator.yml things more or less worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants