Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • P pagedjs-cli
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pagedjs
  • pagedjs-cli
  • Issues
  • #40

Closed
Open
Created Sep 28, 2020 by Boris Budini@kominoshja🛡Owner

Documentation unclear about using the Docker image properly

The documentation is unclear or sparse about how to use the Docker image as a standard user.

As a normal user, I use docker pull pagedmedia/pagejs-cli to fetch the image.

After that I want to docker run .... my.html -o my.pdf in some way from the commandline.

As a user, I don't have any seccomp=seccomp.json file.

Using pagedjs-cli through a maintained Docker image is likely the preferred option rather than installing it using npm install -g pagedjs-cli.

Not sure what must be done to improve the out-of-the-box experience with the Docker image as a drop-in replacement for a locally installed pagedjs-cli.

Edited Sep 28, 2020 by Boris Budini
Assignee
Assign to
Time tracking