Add Dockerfile #3
Labels
No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/delete-me#3
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To allow users to run the CLI from a container, like:
Prototyped here: https://github.com/cerc-io/stack-orchestrator/blob/main/container-build/cerc-laconic-client/Dockerfile
Working on this as part of github action testing/demo
@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
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.
closed in #21