package icon indicating copy to clipboard operation
package copied to clipboard

Local builds, prerequisites

Open radu-matei opened this issue 7 years ago • 4 comments

At the moment, all builder implementation require Docker client locally.

Has it been discussed the possibility of having something similar to Draft that builds and pushes your image without you having anything locally?

Thanks!

radu-matei avatar Dec 19 '17 11:12 radu-matei

Yes, I would love to see support for this!

The 'builder' interface is factored out in each runtime to enable this kind of extensibility.

PRs welcome :)

brendandburns avatar Dec 19 '17 15:12 brendandburns

Ok, so in this case:

  • there will be a pod in the Kubernetes cluster that will create and push the image
  • based on that image, the local mp-compiler will push the deployment on the cluster.

Is this brief overview correct? Do you have anything else in mind? (Maybe the mp-compiler also as a service in the cluster?)

Now, do we also want to enable support for custom a Dockerfile? (Simply as an optional param as path to a local Dockerfile). The way I see from the runtimes, the Dockerfile is created on the fly, and the user doesn't have the ability to have any input anything.

Thanks!

radu-matei avatar Dec 19 '17 16:12 radu-matei

Yeah, sounds about right. mp-compiler is actually built as a RESTful server too, so it can definitely run in a cluster.

--brendan


From: Radu Matei [email protected] Sent: Tuesday, December 19, 2017 8:45 AM To: metaparticle-io/package Cc: Brendan Burns; Comment Subject: Re: [metaparticle-io/package] Local builds, prerequisites (#50)

Ok, so in this case:

  • there will be a pod in the Kubernetes cluster that will create and push the image
  • based on that image, the local mp-compiler will push the deployment on the cluster.

Is this brief overview correct? Do you have anything else in mind? (Maybe the mp-compiler also as a service in the cluster?)

Now, do we also want to enable support for custom a Dockerfile? (Simply as an optional param as path to a local Dockerfile). The way I see from the runtimes, the Dockerfile is created on the fly, and the user doesn't have the ability to have any input anything.

Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmetaparticle-io%2Fpackage%2Fissues%2F50%23issuecomment-352816496&data=02%7C01%7Cbburns%40microsoft.com%7C097685d08cdd4da878d508d546fff02a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636492987433793014&sdata=R0hv%2FgP2FzemZgkXAypjPTpERkbHnH2XwprVGRpPb1k%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFfDgmtkiRcNAx70ynYNdz7KTimSBpU8ks5tB-gzgaJpZM4RG1vS&data=02%7C01%7Cbburns%40microsoft.com%7C097685d08cdd4da878d508d546fff02a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636492987433793014&sdata=1XgnbVKKvw4WA6LUmhp0cnTHGBNFAmx1awUvuIdTiw0%3D&reserved=0.

brendandburns avatar Dec 19 '17 17:12 brendandburns

Related: How is metaparticle expected to interact with CI/CD? #49

stealthybox avatar Dec 20 '17 20:12 stealthybox