VisionSystemsInc / VisionSystemsInc/vsi_common
Bug in parse-docker-compose-volumes with special characters
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8
- Forks
- 9
- Avg merge
- 36m
- Merged PRs (30d)
- 1
Description
If a path has a special character in it, such as a tab, the output of docker-compose config is
services:
test_hay:
volumes:
- "/tmp/f o o\tbar/test-docker_functions.bsh-3685004.q7YBc5ev/test4:/src:rw"
- "/tmp/f o o\tbar/test-docker_functions.bsh-3591660.0AqqVZoq/test4/foo\"b'ar:/src:rw"
- "/tmp/f o o\tbar/test-docker_functions.bsh-3591660.0AqqVZoq/test4/f\U0001F61B\
oo\"b'ar:/src:rw"
parse-docker-compose-volumes does not currently handle this for long or short formats.
Unicode is an issue, and not generally supported.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the parse-docker-compose-volumes entry point and its handling of long and short volume formats. Reproduce the examples with docker-compose config, then inspect any related tests or parsing logic; done means paths containing tabs, quotes, spaces, and similar special characters are handled in both formats, while Unicode remains unsupported as stated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100