Add ghrc container

[ankudinov]

Start building marp-cli container on GHRC.
Fixes #578

[ankudinov]

The workflow is currently hardcoded to build on my branch to test before merging.
Do not move out of draft status before changing that.

[ankudinov]

@yhatt I'd appreciate some help explaining the current Dockerfile logic. Unfortunately I have 0 skills in Node and it can be something trivial.
However my build is using existing Dockerfile and fails with the following error:

#10 25.06 Error: Cannot find module './lib/marp-cli.js'

This probably comes from marp-cli.js:

marp-cli/marp-cli.js

Line 5 in 37cd008

require('./lib/marp-cli.js')

I can not get how this file supposed to be created. The Dockerfile COPY --chown=marp:marp . . definitely not helping.

[ankudinov]

Here is the latest build log for the reference: https://github.com/ankudinov/marp-cli/actions/runs/9383539973/job/25837379955

[yhatt]

Is #515 helpful?

[yhatt]

Marp team is currently using CircleCI to push the image to Docker Hub. The triggers and build steps are following:

• When updated main branch:
  1. CI will run the test for every supported Node.js versions. →
  2. If all tests passed, CI will build Marp CLI with the build command yarn build. At this time, necessary files will be generated in the lib directory. →
     • CI will store the lib directory as artifacts. (It calls "workspaces" in CircleCI)
     • Currently we are not building Marp CLI within Dockerfile, for making faster the build process for multi-arch images: Update Dockerfile to copy pre-built code in /lib into image #402
  3. After building, CI will restore previously stored artifacts, build the multi-arch image linux/amd64 and linux/arm64 (for Apple Silicon), and publish it to the Docker Hub with latest tag. →

• When pushed the tag starting with v.:
  1. CI will build Marp CLI and generate the lib directory.
  2. After building, CI will build and publish the image tagged with the version number.