Add Dockerfile #3

Closed
opened 2022-09-29 03:05:52 +00:00 by dboreham · 4 comments
Owner

To allow users to run the CLI from a container, like:

$ docker run cerc/laconic-client:local --help
laconic <command>

Commands:
  laconic cns  CNS tools

Options:
      --version  Show version number                                   [boolean]
  -v, --verbose  Verbose output                       [boolean] [default: false]
  -c, --config   Config file path.              [string] [default: "config.yml"]
      --help     Show help                                             [boolean]

Prototyped here: https://github.com/cerc-io/stack-orchestrator/blob/main/container-build/cerc-laconic-client/Dockerfile

To allow users to run the CLI from a container, like: ``` $ docker run cerc/laconic-client:local --help laconic <command> Commands: laconic cns CNS tools Options: --version Show version number [boolean] -v, --verbose Verbose output [boolean] [default: false] -c, --config Config file path. [string] [default: "config.yml"] --help Show help [boolean] ```` Prototyped here: https://github.com/cerc-io/stack-orchestrator/blob/main/container-build/cerc-laconic-client/Dockerfile
ABastionOfSanity commented 2023-02-14 17:22:58 +00:00 (Migrated from github.com)

Working on this as part of github action testing/demo

Working on this as part of github action testing/demo
ABastionOfSanity commented 2023-02-14 17:25:59 +00:00 (Migrated from github.com)
@dboreham Should this just use: https://github.com/cerc-io/stack-orchestrator/blob/main/app/data/container-build/cerc-laconic-registry-cli/Dockerfile#L55 as mentioned here: https://github.com/cerc-io/laconic-registry-cli/issues/15#issuecomment-1379125090
Author
Owner

Yes, I think this issue report pre-dates S-O, and certainly the Dockerfile there.
But, ideally I think the Dockerfile should be in this repo. That's the model we use where possible.
The presence of a Dockerfile in the S-O repo indicates that there wasn't one, or a usable one in the target project.
So tentatively I'd move the Dockerfile here and we can update S-O to use it vs having its own one.

Yes, I think this issue report pre-dates S-O, and certainly the Dockerfile there. But, ideally I think the Dockerfile should be in _this_ repo. That's the model we use where possible. The presence of a Dockerfile in the S-O repo indicates that there wasn't one, or a usable one in the target project. So tentatively I'd move the Dockerfile here and we can update S-O to use it vs having its own one.
Member

closed in #21

closed in #21
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/laconic-registry-cli#3
No description provided.