Support for: top-level volumes.

[cdrage]

Using a top-level volume errors out and is unsupported:

version: "2"

services:
    redis:
      image: redis:3.0

volumes:
  - /var/lib/mysql

ERRO Could not parse config for project wikus : yaml: unmarshal errors:
  line 8: cannot unmarshal !!seq into map[string]interface {} 
FATA Failed to load compose file: yaml: unmarshal errors:
  line 8: cannot unmarshal !!seq into map[string]interface {} 

[cdrage]

@surajnarwade @procrypt

Is it possible to investigate this to see what we could possibly do to implement it?

Of course, other top-level keys such as networks makes sense not to support, but volumes seems important.

[procrypt]

@cdrage Will look into it. @surajnarwade Do you have some time today we can discuss about it.

[surajnarwade]

@procrypt sure

[surajnarwade]

@cdrage , I think top-level volumes keys dont make any sense.

[cdrage]

@surajnarwade Could you give your reasoning as to why they don't make sense?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[cdrage]

Ping @surajnarwade

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[surajnarwade]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[cdrage]

Don't we support this now @hangyan ? I think we do..

[hangyan]

@cdrage No, we haven't...

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close