[
https://issues.apache.org/jira/browse/CALCITE-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733586#comment-16733586
]
Francis Chuang edited comment on CALCITE-2579 at 1/3/19 10:26 PM:
------------------------------------------------------------------
I am considering dropping skaffold in favor of docker-compose and
[reflex|https://github.com/cespare/reflex]. Skaffold requires access to a
kubernetes-cluster and while it's possible to run one locally with minikube or
docker-for-windows, the extra bits take up precious memory. Another problem
with skaffold is that it builds a new docker image on every reload, so you end
up with a bunch of docker images that you need to delete manually. This is
scriptable of course, but it's a complexity I prefer we avoid.
was (Author: francischuang):
I am considering dropping skaffold in favor of docker-compose and
[reflex|[https://github.com/cespare/reflex]|https://github.com/cespare/reflex]/].
Skaffold requires access to a kubernetes-cluster and while it's possible to
run one locally with minikube or docker-for-windows, the extra bits take up
precious memory. Another problem with skaffold is that it builds a new docker
image on every reload, so you end up with a bunch of docker images that you
need to delete manually. This is scriptable of course, but it's a complexity I
prefer we avoid.
> Replace moby with skaffold
> --------------------------
>
> Key: CALCITE-2579
> URL: https://issues.apache.org/jira/browse/CALCITE-2579
> Project: Calcite
> Issue Type: Task
> Components: avatica-go
> Reporter: Francis Chuang
> Assignee: Francis Chuang
> Priority: Major
> Fix For: avatica-go-4.0.0
>
>
> moby.yml is used by an internal tool (moby) used to run tests while
> developing the avatica-go library. It reloads the code in a docker container
> and executes tests.
> [Skaffold |https://github.com/GoogleContainerTools/skaffold] is maintained by
> Google and achieves the same thing. Initial testing has shown that it works
> pretty well and most of the issues I encountered a few months ago were all
> resolved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
