emptyvols option doesn't work for kompose convert/up

[ashetty1]

kompose convert and kompose up fails with emptyvols option:

$ kompose version
0.7.0 (c25b7e8)

$ kompose --provider=openshift --emptyvols -f examples/docker-compose.yaml convert -h
Error: unknown command "examples/docker-compose.yaml" for "kompose"
Run 'kompose --help' for usage.
unknown command "examples/docker-compose.yaml" for "kompose"

Without emptyvols option:

$ kompose --provider=openshift -f examples/docker-compose.yaml convert
INFO file "frontend-service.yaml" created         
INFO file "redis-master-service.yaml" created     
INFO file "redis-slave-service.yaml" created      
INFO file "frontend-deploymentconfig.yaml" created 
INFO file "frontend-imagestream.yaml" created     
INFO file "redis-master-deploymentconfig.yaml" created 
INFO file "redis-master-imagestream.yaml" created 
INFO file "redis-slave-deploymentconfig.yaml" created 
INFO file "redis-slave-imagestream.yaml" created 

Same issue is seen with kompose up, and has been documented here #614

[rawkode]

Taking a look at this 👍

[surajnarwade]

@ashetty1 , this is weird but if I run, I got error,

$ kompose --provider=openshift --emptyvols -f kompose/examples/docker-compose.yaml convert
Error: unknown command "kompose/examples/docker-compose.yaml" for "kompose"
Run 'kompose --help' for usage.
unknown command "kompose/examples/docker-compose.yaml" for "kompose"

but if I run it as,

$ kompose --provider=openshift  -f kompose/examples/docker-compose.yaml convert --emptyvols 
INFO file "frontend-service.yaml" created         
INFO file "redis-master-service.yaml" created     
INFO file "redis-slave-service.yaml" created      
INFO file "frontend-deploymentconfig.yaml" created 
INFO file "frontend-imagestream.yaml" created     
INFO file "redis-master-deploymentconfig.yaml" created 
INFO file "redis-master-imagestream.yaml" created 
INFO file "redis-slave-deploymentconfig.yaml" created 
INFO file "redis-slave-imagestream.yaml" created 

it worked :)

[ashetty1]

@surajnarwade yes. I saw the same behaviour too. If --emptyvols is passed after up/down, it works. Weird indeed.

[surajnarwade]

@kadel , is it intentional ?

[kadel]

yes, that is intentional.
--emptyvol is not a global flag, so it has to be specified after subcommand.

[ashetty1]

Closing this.