app upload from existing docker image

[cocaine]

app upload from existing docker image

[andrusha97]

Also it's not clear from docs what should I specify in slave option

You always should specify slave. Cocaine provides some command line arguments to your program (to a framework actually), so it composes command to be run on its own, and the default command is always ignored.

[cybernetlab]

You always should specify slave. Cocaine provides some command line arguments to your program (to a framework actually), so it composes command to be run on its own, and the default command is always ignored.

@andrusha97 Just for proposal. Maybe it would be better to provide these arguments via env var or in some other way, because current manner breaks docker run as executable manner. I see that docker is not a central point of overall system but maybe it's possible to change behaviour of just docker.io applications?

[noxiouz]

To make an application visible in cocaine, manifest should be uploaded. In case of Docker isolation we needn't store the application code. Application name must be the same as image name, and endpoint of Docker registry is specified in profile. So it seems to be enough to add an abilty to upload only a manifest without image building. @3Hren, What do you thing abiout it?

When it comes to passing arguments by other way. Unfortunately, it's impossible now in the current stable version, as all frameworks parse agrv to get an application name, uuid, endpoint. It doesn't matter for framework what type of isolation is used to isolate. May be in the next version of cocaine.... Anyway we will think about it. Thanks!

[3Hren]

Looks reasonable for me.

[cybernetlab]

Thanks for your project! And for neat response! ;)

[kobolog]

Actually, passing the args as environment variables was discussed a couple of times already, and I think it has all the chances to make it into the next release.