Error using latest docker image
See original GitHub issueHi,
I’m trying to convert a reveal.js html presentation to pdf using the latest docker image.
I got this error :
# ls -l |grep slides
-rw-r--r--. 1 root root 3207230 Jul 17 18:59 slides.html
# docker run --rm -t -v `pwd`:/slides -v ~:/home/user astefanutti/decktape /home/user/slides.html slides.pdf
TypeError: Unable to create PDF file, make sure that output file target is available
at /decktape/decktape.js:196:26
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:182:7)
Can anyone tell me what do I do wrong?
Many thanks in advance, Kind regards
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
What's Wrong With The Docker :latest Tag? - vsupalov.com
If you're working with an image which is tagged with “latest”, that's all the information you have apart from the image ID.
Read more >No Such Image found error even though there is image ...
Problem Statement : I am using private docker registry for docker image. Image with correct name:tag is available in private docker registry ...
Read more >Error running latest docker image · Issue #106 - GitHub
Hi! My CI pipeline tries to pull the latest docker image available on dockerhub and run it. I just got the following error...
Read more >Why Am I Getting A Docker Image Tagging Error Response?
When I run docker images it returns the images I have loaded. Here are two for example. REPOSITORY TAG IMAGE ID CREATED SIZE...
Read more >Solving 'manifest not found' Error While Pulling Docker Images
Here are some tips on troubleshooting the common 'unknown manifest' error while pulling a Docker image.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for your answer. I can’t run docker without sudo. That made me think to the --privileged option in docker.
I successfully ran this command :
We can then consider this issue as solved 😃
Hi can actually replicate the issue by read-only mounting the output directory, e.g.:
So it tends to indicate this is a permission issue with the output directory / file.
Could you try by explicitly read-write mounting the output directory with:
Maybe it’s a particular configuration of your Docker daemon. Besides, would you be able to run the command without
sudo
.