You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maintaining the vagrant-baseimage is difficult since we lack
suitable automation facilities. It has therefore become an
impediment to producing new docker baseimages. In addition,
it is also less important these days since most of the heavy
lifting is performed by the docker infrastructure.
Consider that when the baseimage for vagrant was created, we
still needed to compile a bunch of basic tools (golang, protobufs
rocksdb, etc). This is no longer true: Some of the tools
are now available in binary form, others are exectuted within
docker, and others are no longer used (e.g. rocksdb).
Therefore, we can greatly simplify our processes by simply
eliminating our reliance on a precompiled baseimage for
vagrant. Because of the dockerization effort, all we really
need is a basic platform with make, git, golang-1.7, and docker.
We also include a few other items for developer convenience,
such as behave, nodejs, and java.
Fixes FAB-3000
Change-Id: Ic0749a1c0361a0b4a83d7ca6879e9d2bb50a5456
Signed-off-by: Gregory Haskins <[email protected]>
config.vm.box_version=ENV['USE_LOCAL_BASEIMAGE'] ? "0": baseimage_release# Vagrant does not support versioning local images, the local version is always implicitly version 0
34
+
config.vm.box="ubuntu/xenial64"
38
35
39
36
config.vm.network:forwarded_port,guest: 7050,host: 7050# fabric orderer service
40
37
config.vm.network:forwarded_port,guest: 7051,host: 7051# fabric peer service
0 commit comments