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

command instruction not supported in compose file #2365

Closed
ghost opened this issue Sep 7, 2016 · 5 comments
Closed

command instruction not supported in compose file #2365

ghost opened this issue Sep 7, 2016 · 5 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Milestone

Comments

@ghost
Copy link

ghost commented Sep 7, 2016

Reproduction Steps:

Use:

command: tail -f /dev/null

in the compose file.

Expected behavior:

Command is executed

Observed behavior:

Error parsing compose file

Currently command is accepted as:

command: [tail, -f, /dev/null]

@ghost ghost added the kind/bug Outline of a bug - must adhere to the bug report template. label Sep 7, 2016
@garagatyi garagatyi self-assigned this Sep 7, 2016
@garagatyi garagatyi added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/production labels Sep 7, 2016
@garagatyi
Copy link

Please provide an example of compose file you used to reproduce behavior

@ghost
Copy link
Author

ghost commented Sep 12, 2016

services:
 db:
  image: codenvy/mysql
  environment:
   MYSQL_USER: petclinic
   MYSQL_PASSWORD: password
  mem_limit: 2147483648
  command: service mysql start
 dev-machine:
  image: codenvy/ubuntu_jdk8
  mem_limit: 2147483648
  depends_on:
    - db

@garagatyi
Copy link

Since command nature is an array of strings and this instruction is parsed in YAML as a single string compose has to have custom parsing rules to use such syntax.
We haven't implemented that custom logic yet.

@bmicklea bmicklea added this to the 5.0.0-M6 milestone Sep 30, 2016
@vkuznyetsov vkuznyetsov added sprint/next team/enterprise status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach and removed team/production status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Oct 6, 2016
@bmicklea
Copy link

@vkuznyetsov can you check to see if it can be completed for 18-Oct?

@vkuznyetsov vkuznyetsov added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. sprint/current and removed sprint/next status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach labels Oct 13, 2016
@AndrienkoAleksandr AndrienkoAleksandr self-assigned this Oct 17, 2016
@AndrienkoAleksandr AndrienkoAleksandr added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Oct 17, 2016
@AndrienkoAleksandr AndrienkoAleksandr added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. status/in-progress This issue has been taken by an engineer and is under active development. and removed status/in-progress This issue has been taken by an engineer and is under active development. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Oct 18, 2016
@AndrienkoAleksandr AndrienkoAleksandr added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Oct 25, 2016
@riuvshin riuvshin modified the milestones: 5.0.0-M7, 5.0.0-M6 Oct 26, 2016
@riuvshin
Copy link
Contributor

Moved to M7 because it is still in progress.

@bmicklea bmicklea modified the milestones: 5.0.0-M8, 5.0.0-M7 Nov 8, 2016
@vkuznyetsov vkuznyetsov removed sprint/current status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Nov 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

5 participants