Re: GitHub Actions - openBinaryFile: does not exist (No such file or directory)

[Shakrmaker <tojonmz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 3114 bytes --]

Thanks John. I'm still searching for where the -v arg is used which maps 
the volumes. So far, no luck searching in:
https://github.com/pandoc/dockerfiles

I see:
https://github.com/pandoc/dockerfiles/blob/master/ubuntu/Dockerfile#L73

I've also tried to ls /data in an action run. I can, but that clearly is 
not where my repo is being delivered inside the container.

Clearly, I don't understand where convert_via_pandoc is that the yaml 
calls, or where the arguments are.

On Monday, June 28, 2021 at 1:29:55 PM UTC-4 John MacFarlane wrote:

>
> Take a look at the docker command. The -v option is being used
> to map your directory to a different directory in the docker
> image, so you'll have to use a different path.
>
> Shakrmaker <toj...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > Hi Everyone,
> >
> > Apologies, but I've searched all the threads here (StackOverflow, etc), 
> and 
> > while I've found lots of folks hitting it, I haven't found my solution. 
> I 
> > set up a GitHub Action in my repo on push, essentially using the 
> provided 
> > example on https://github.com/pandoc/pandoc-action-example.
> >
> > I can run and access my input files fine with a simple run ls, via an 
> > /absolute/path, via ${{ github.workspace }}/path, or via 
> > $GITHUB_WORKSPACE/path so I know they are there.
> >
> > But when I try to call pandoc with the yaml, I get the classic error:
> > pandoc: *(my-valid/path*): openBinaryFile: does not exist (No such file 
> or 
> > directory)
> >
> > My yaml:
> >
> > on: push
> >
> > jobs:
> > convert_via_pandoc:
> > runs-on: ubuntu-18.04
> > steps:
> > # Checks-out repository under $GITHUB_WORKSPACE, so job can access it
> > - uses: actions/checkout@v2
> > - run: ls [valid/path].md
> > - uses: docker://pandoc/core:2.11.2
> > with:
> > args: >- # break args into multiple lines
> > -s
> > -M title="My Title"
> > -o output.html
> > -f markdown
> > [valid/path].md
> >
> > Here's an example showing the path is valid, and the failure when I try 
> to 
> > access that path as the input file (same occurs using $GITHUB_WORKSPACE, 
> > etc).
> >
> > I am a newbie to both GitHub Actions and Pandoc, so it must be something 
> > obvious to the experts here. What am I doing wrong?
> >
> > Thanks in advance.
> >
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "pandoc-discuss" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/06a85c25-bad6-4c22-a184-a3becb9f64dbn%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b9b67058-9a97-471a-b6d6-0021ea504a36n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4854 bytes --]