Skip to content

Conversation

@carlwilson
Copy link
Contributor

  • replaced used of CMD with ENTRYPOINT in Dockerfile;
  • fixed the instructions for using the Docker image for ENTRYPOINT invocation; and
  • expose the /app folder as VOLUME.

The issues below detail the thinking:

Closes #945, #946

- replaced used of `CMD` with `ENTRYPOINT` in Dockerfile.

See this [Docker blog](https://www.docker.com/blog/docker-best-practices-choosing-between-run-cmd-and-entrypoint/) for rationale assuming this container is intended as a pdfcpu one trick pony.
- fixed the instructions for using the Docker image for `ENTRYPOINT` invocation; and
- expose the `/app` folder as `VOLUME`.
@hhrutter
Copy link
Collaborator

hhrutter commented Sep 9, 2024

Hi!
I am not a docker expert/captain..
Is there any way to modify the docker file so the container executes and outputs pdfcpu version -v on startup?

@carlwilson
Copy link
Contributor Author

carlwilson commented Sep 9, 2024

Hi,
I understand the question and why you're asking it. I fear the answer is not alongside the help. It's either the help OR the version a default, but not both. I'm happy to try some ideas and get back to you. It might be a couple of weeks as time is currently a little tight,

@hhrutter hhrutter merged commit 007356f into pdfcpu:master Sep 12, 2024
@hhrutter
Copy link
Collaborator

Thank you for your contribution!

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

Successfully merging this pull request may close these issues.

Use Docker ENTRYPOINT rather than CMD

2 participants