Copy config under a volume for Docker (similar to a ConfigMap for K8S). #914
Labels
Clear labels
K8s
bug
documentation
duplicate
enhancement
feature
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
Something isn't working
Improvements or additions to documentation
This issue or pull request already exists
New feature or request
Good for newcomers
Extra attention is needed
This doesn't seem right
Further information is requested
This will not be worked on
An issue or PR manually copied from GitHub.
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/stack-orchestrator#914
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This emulates the K8S ConfigMap behavior on Docker by using a regular volume.
If a directory exists under
config/which matches a named volume, the contents will be copied to the volume oncreate(provided the destination volume is empty). That is, rather than a ConfigMap, it is essentially a "config volume".For example, with a compose file like:
And a directory:
After
laconic-so deploy create --spec-file caddy.yml --deployment-dir /srv/caddythere will be:Mounted at
/etc/caddyCopy config under a volume for Docker too (similar to a configmap).to Copy config under a volume for Docker (similar to a ConfigMap for K8S).