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

Unsupported root level networks key despite no networks #365

Closed
cdrage opened this issue Jan 6, 2017 · 2 comments
Closed

Unsupported root level networks key despite no networks #365

cdrage opened this issue Jan 6, 2017 · 2 comments

Comments

@cdrage
Copy link
Member

cdrage commented Jan 6, 2017

The warning could be a bit more descriptive, but upon converting:

▶ cat script/test/fixtures/tty-true/docker-compose.yml 
version: "2"
services:
  client:
    image: registry.centos.org/centos/centos:7
    ports:
    - "1337"
    tty: true

It appears to output a warning in regards to a root level network, despite none being defined.

github.com/kubernetes-incubator/kompose  update-vendoring ✔                                                                                                                                                                                                                  2d
▶ kompose -f /home/wikus/dropbox/dev/go/src/github.com/kubernetes-incubator/kompose/script/test/fixtures/tty-true/docker-compose.yml convert --stdout -j
WARN[0000] Unsupported root level networks key - ignoring
{                            
  "kind": "List",
  "apiVersion": "v1",
  "metadata": {},          
  "items": [      
    {                            
      "kind": "Service",                                       
      "apiVersion": "v1",     
      "metadata": {      
@surajnarwade
Copy link
Contributor

@cdrage , I tried same docker compose file, there's no warning, I think issue is resolved now, we can close this,

output is:

$ kompose -f docker-compose.yml convert --stdout -j
{
  "kind": "List",
  "apiVersion": "v1",
  "metadata": {

@cdrage
Copy link
Member Author

cdrage commented Mar 22, 2017

@surajnarwade You're right, this is no longer an issue. Closing! 👍

@cdrage cdrage closed this as completed Mar 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants