Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DOCKER_CONFIG has more priority than WERF_DOCKER_CONFIG #5161

Open
1 task done
distorhead opened this issue Dec 16, 2022 · 0 comments
Open
1 task done

DOCKER_CONFIG has more priority than WERF_DOCKER_CONFIG #5161

distorhead opened this issue Dec 16, 2022 · 0 comments
Labels
priority: low scope: common type: bug

Comments

@distorhead
Copy link
Member

distorhead commented Dec 16, 2022 •
edited
Loading

Before proceeding

  • I didn't find a similar issue

Version

1.2.192

How to reproduce

WERF_DOCKER_CONFIG should be prioritized over DOCKER_CONFIG because it is more focused specific parameter than generic DOCKER_CONFIG.

Additional information

No response
@distorhead distorhead changed the title DOCKER_CONFIG has more priority than WERF_DOCKER_CONFIG Bug: DOCKER_CONFIG has more priority than WERF_DOCKER_CONFIG Dec 16, 2022
@alexey-igrychev alexey-igrychev changed the title Bug: DOCKER_CONFIG has more priority than WERF_DOCKER_CONFIG DOCKER_CONFIG has more priority than WERF_DOCKER_CONFIG Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: low scope: common type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@distorhead @alexey-igrychev