Closed 1999 closed 2 years ago
You can't provide relative paths like ~/Downloads/271556.cast and ~/Downloads/271556.gif. They don't exist inside docker container.
You can't provide relative paths like ~/Downloads/271556.cast and ~/Downloads/271556.gif. They don't exist inside docker container.
@umrashrf
not sure if that is entirely true or not as i just passed the below commmand on macOS,
docker run --rm -v $PWD:/data asciinema/asciicast2gif -s 2 ./git-squash-commits.json ./wtfff.gif
and it seems the docker process begins to process the path to file, and on a separate note you can see the node process expands ~
to /Users/dsorin
his stacktrace.
All that said, I believe the issue relies in how he has docker configured on his system, 99% sure he/she is running macOS due to seeing the following directory structure /Users/dsorin
and the issue is related to how he/she has setup bind mounted directories within the preferences of the docker app itself, as I was running into the exact same issue as described by @1999 ,but when I moved my recorded cast file to a path specified within the File Sharing tab of docker preferences window, the container was able to process the cast file.
Error: ENOENT: no such file or directory, open '/Users/dsorin/Downloads/271556.cast'
It evaluates the path correctly based on current host user but that path might not exist in guest docker.
Closing as asciicast2gif is dead. Try https://github.com/asciinema/agg instead.
I'm trying to run
asciicast2gif
on my computer like this:docker run --rm -v $PWD:/data asciinema/asciicast2gif ~/Downloads/271556.cast ~/Downloads/271556.gif
For this command, I get this output:
But when I cd into /Users/dsorin/Downloads/ and run:
docker run --rm -v $PWD:/data asciinema/asciicast2gif 271556.cast 271556.gif
looks like everything works.