### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [June 16, 2017, 4:20pm UTC](https://discuss.bitrise.io/t/weekly-virtual-machine-stack-updates-2017-06-17/2042/1 "2017-06-16T16:20:19Z")
## Highlights
Bitrise CLI 1.6.2 preinstalled on all stacks. Related CLI release announcement:
> [@Monthly release of Bitrise CLI tools and summary of updates (Jun, 2017) - CLI v1.6.2](http://discuss.bitrise.io/t/monthly-release-of-bitrise-cli-tools-and-summary-of-updates-jun-2017-cli-v1-6-2/2012):
>
> We ship a new bitrise cli version on the second Tuesday of every month. The new release will be available on the [bitrise.io](https://www.bitrise.io) virtual machines on the weekend after the CLI release, unless we discover any serious bug / regression. Read on to learn more about this month’s [Bitrise CLI](https://github.com/bitrise-io/bitrise) release and about the changes around bitrise tools and steps. New version of Bitrise CLI ([1.6.2](https://github.com/bitrise-io/bitrise/releases/tag/1.6.2)) plugin info command bitrise-cli got a new command: bitrise plugin info Prints infos about the specified installe…
### Android/Linux stacks
- Android platform 26 and build-tools 26.0.0 preinstalled
- Thanks @koral for the [PR](https://github.com/bitrise-docker/android/pull/88)!
- Android NDK upgrade to r15
- Thanks @koral for the [PR](https://github.com/bitrise-docker/android-ndk/pull/64)!
### Xcode stacks
- No significant change other than the Bitrise CLI upgrade
### Xamarin stacks
- No significant change other than the Bitrise CLI upgrade
## This week’s changes (diffs)
>
## Stack System Reports
You can find the full system report of all of the available Stacks on GitHub: [https://github.com/bitrise-io/bitrise.io/tree/master/system\_reports](https://github.com/bitrise-io/bitrise.io/tree/master/system_reports).
If you’d like to add additional tools to be pre-installed you can find the instructions on [GitHub](https://github.com/bitrise-io/bitrise.io#request-a-tool-to-be-pre-installed-on-a-build-machine), for both the Linux and for the macOS stacks.
_Information about **Stack types & update schedules** can be found here: [discuss.bitrise.io/t/281](http://discuss.bitrise.io/t/how-are-the-bitrise-io-stacks-updated-and-with-what-frequency/281)._
**Happy Building!**
---
### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [June 16, 2017, 4:21pm UTC](https://discuss.bitrise.io/t/weekly-virtual-machine-stack-updates-2017-06-17/2042/2 "2017-06-16T16:21:03Z")
All stacks passed our tests and ready for deploy at Saturday 🚀
---
### Author:  [@wkd](https://discuss.bitrise.io/u/wkd)
#### Post date: [June 16, 2017, 7:02pm UTC](https://discuss.bitrise.io/t/weekly-virtual-machine-stack-updates-2017-06-17/2042/3 "2017-06-16T19:02:58Z")
How does one contribute a stack? Our Docker Images for ASP Dot Net core are public. And we’re also working on another project involving meteor Cordova.
[https://hub.docker.com/u/weknowdeals/](https://hub.docker.com/u/weknowdeals/)
- docker-bitrise-dotnetcore
- docker-bitrise-meteor-cordova
- docker-bitrise-postgres
and can be reviewed - can always be forked under bitrise management. All we want is the caching if possible. Because our builds are taking time to pull from docker hub.
---
### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [June 17, 2017, 8:14am UTC](https://discuss.bitrise.io/t/weekly-virtual-machine-stack-updates-2017-06-17/2042/4 "2017-06-17T08:14:40Z")
> [@wkd](#):
>
> Our Docker Images for ASP Dot Net core are public. And we’re also working on another project involving meteor Cordova
Awesome, it’s fantastic to see! 🙂
I wonder if we should create a topic or category here on [discuss.bitrise.io](http://discuss.bitrise.io) for sharing Docker images with each other. There are a few other teams who also have images built on top of the bitrise images, although this “club” would be quite exclusive at the start (we only know about 2-3 teams who do this).
> [@wkd](#):
>
> All we want is the caching if possible. Because our builds are taking time to pull from docker hub.
For now the solution is to make your images as small as possible, compacting your layer.
We do plan to provide caching option for docker images, but that won’t come in the next weeks/months unfortunately.
---
### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [June 17, 2017, 11:24am UTC](https://discuss.bitrise.io/t/weekly-virtual-machine-stack-updates-2017-06-17/2042/5 "2017-06-17T11:24:48Z")
New stacks deployed and are available in production 🎉