kernelci / kernelci/kernelci-pipeline
Fix path loading for docker runtime
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 40
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 14
Description
These lines require absolute paths, as the comment says, but the absolute paths depend on each individual setup.
When relative paths are used, docker fails with this message:
400 Client Error for http+docker://localhost/v1.41/containers/create: Bad Request ("create data/ssh/: "data/ssh/" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path")
which isn't handled gracefully.
Find a way to make this either more robust, or clearer to the user (force the user to set an absolute path, or set it automatically), or remove the issue completely.
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 at config/pipeline.yaml line 79 and reproduce the Docker container creation error with a relative path. Determine whether the project should resolve paths automatically or reject them with a clear message; done means the path-loading behavior is robust or the user-facing failure is explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100