-
Notifications
You must be signed in to change notification settings - Fork 177
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
'make tar' to use docker compiled assets #1008
Conversation
Makefile
Outdated
|
||
# build tarball | ||
tar: compile-with-docker | ||
docker run --rm netplugin-build:$(NETPLUGIN_CONTAINER_TAG) \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use docker cp
to copy build artifacts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is no container to target docker cp
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
switching to docker create + docker cp + docker rm
b2fe667
to
86cb2c8
Compare
Beacuse of start/stop of a VM, a tar build can take 4 minutes. When using a docker container, when previously compiled only needs 10s (30s if netplugin src updated) Add target to export tar from container build to local directory Signed-off-by: Chris Plock <chrisplo@cisco.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
build PR |
this (and compile-with-docker) works in VM (docker 1.12) as well as desktop (docker 17.09), though without a private registry to cache things like the golang layer, the startup cost of compiling in docker on a fresh VM is large, better to run this target locally. |
make tar
is primarily used for release, it is much faster to use compile-with-docker locally than spawn a VM to run the build.Signed-off-by: Chris Plock chrisplo@cisco.com