VisionSystemsInc / VisionSystemsInc/vsi_common

docker_compose_override: Handling windows paths on WCOW

Open
#169 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug enhancement just windows
Dominant language
Shell
Stars
8
Forks
9
Avg merge
36m
Merged PRs (30d)
1

Description

There are a number of issues when it comes to handling lcow, wcow, and lcol, in docker compose override. It needs to be overhauled to handle all three gracefully

  • Instead of Putting values of always putting variables in directly using bash in directions, for linux containers, this should be done, but for windows containers instead the variable names should be put in, this way bash path conversions will convert them to windows paths. This will work for both environment variables and volumes
  • Since a large part of the dynamic volume code will have to be rewritten for this, we should take the time to support mount instead of volumes: Proposed ideas
    • While arrays will still be supported, arrays will be internally converted to environment variables PROJECT_MOUNT_3, etc...
    • There will be a number of variables to check, PROJECT_MOUNT_SOURCE_1, PROJECT_MOUNT_DESTINATION_1, PROJECT_MOUNT_TYPE_1 (where type can be auto filled in based on if it starts with a / or not. Maybe even optional PROJECT_MOUNT_READONLY_1, etc...
    • Direct VOLUME support will be discontinued, it will always translate into volume.
    • The behavior of directories being created if they don't exist will not be replicated
    • optional idea: Volumes can even be added to the volumes: section.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the docker_compose_override implementation and its dynamic volume handling; the issue does not name files or tests. Review the existing LCOW, WCOW, and LCOW behavior, then define completion against the requested Windows path handling and mount-variable support.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, shell
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.