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.

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

Implement args syntax of build section in compose environment #2661

Closed
2 tasks
garagatyi opened this issue Sep 29, 2016 · 14 comments
Closed
2 tasks

Implement args syntax of build section in compose environment #2661

garagatyi opened this issue Sep 29, 2016 · 14 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@garagatyi
Copy link

Compose supports build arguments https://docs.docker.com/compose/compose-file/#/args .
This feature should not support evaluation of value of arg from environment of host.

Tasks:

  • implement basic support of args
  • add possibility to forbid some names of args or prefixes
@garagatyi garagatyi added kind/enhancement A feature request - must adhere to the feature request template. team/enterprise labels Sep 29, 2016
@bmicklea
Copy link

@l0rd or @mmorhun do you think this is something you can help with? Alex is going on vacation and it would be great to get this added into our compose syntax.

@l0rd
Copy link
Contributor

l0rd commented Sep 29, 2016

@bmicklea I can start working on that Wednesday next week. If it's not too late I would love to take that.

@bmicklea
Copy link

That's great @l0rd thank you!

@bmicklea bmicklea added this to the 5.0.0-M6 milestone Sep 30, 2016
@bmicklea
Copy link

bmicklea commented Oct 4, 2016

This is critical to M6.

@l0rd
Copy link
Contributor

l0rd commented Oct 5, 2016

I'm working on that. I will provide an update tomorrow.

@bmicklea
Copy link

bmicklea commented Oct 5, 2016

Thanks very much Mario!

@vkuznyetsov vkuznyetsov added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. sprint/next labels Oct 6, 2016
@l0rd
Copy link
Contributor

l0rd commented Oct 6, 2016

@bmicklea I will provide a PR for the first task tomorrow, monday in the worst case.

The second task (add possibility to forbid some names of args or prefixes) is not clear to me. Why should we forbid some names/prefixes? Which ones are we going to forbid? Since @garagatyi is on vacation can someone else can answer my questions?

@bmicklea
Copy link

bmicklea commented Oct 7, 2016

Thanks Mario, that's great news!

I am not sure what Alex what thinking with that one Mario - are there perhaps args or prefixes that could cause bad behaviors in the system?

@skabashnyuk @gazarenkov is there anyone else who might have an idea of what Alex was considering with his second subtask?

@l0rd
Copy link
Contributor

l0rd commented Oct 10, 2016

@bmicklea @skabashnyuk @gazarenkov @garagatyi I've submitted PR #2749 to address the first task.

For the second task ("add possibility to forbid some names of args or prefixes") it's maybe related to some CHE environment variables that we don't want to be overwritten by users?

@vkuznyetsov vkuznyetsov removed sprint/next status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/enterprise labels Oct 11, 2016
@bmicklea
Copy link

@l0rd we will split this into two issues. Your PR is fine to fix the first task and we will move the second task to its own issue.

@bmicklea
Copy link

Second part of this issue is being separately tracked with #2760.

@l0rd
Copy link
Contributor

l0rd commented Oct 11, 2016

@bmicklea that makes sense

@garagatyi
Copy link
Author

The idea of the limitation is that in case of usage of docker management tool such as Swarm args can have impacts on the system where image is built. I don't have any particular example of such vulnerability, it is just a suggestion that there are some.

@bmicklea
Copy link

bmicklea commented Oct 19, 2016

Closeing - PR merged. Thanks l0rd!

@bmicklea bmicklea mentioned this issue Oct 28, 2016
26 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

4 participants