Has google published distroless image for JDK 13? If not, what's the best alternative to use for JDK 13?
I'd suggest the openjdk images. Distroless is oriented towards long-term support images (LTS). Java 13 is not an LTS image and I'm not aware of any organizations that are supporting Java 13 beyond the end of this month (March 2020).
Related
How to download quickstart VM 5.x for virtual box for windows 10? I have installed oracle virtual box. But for cloudera qickstart VM I am not getting any source. I have searched a lot in google and youtube but the link or site all are referring is no more there. Can anyone please help?
The first thing to realize, is that a VM which can be run on any operating system by leveraging tools like VMware and Virtual Box.
Cloudera in fact no longer provides a quickstart VM for the legacy CDH 5 platform, this can be seen here as you get redirected to CDP datacenter.
However be aware that CDH 5 relates to a very old distribution. I believe CDH 5 goes end of life this year. Even CDH 6 is not recommended for new clusters, as CDP 7 is already GA for a while. CDP, the Cloudera Data Platform is the successor to both CDH and HDP.
If you want to check out the latest version, there is a trial which should serve for most purposes that you may wanted to use the quickstart. This can be downloaded here.
Full disclosure: I am an employee of Cloudera, the company behind both CDH and CDP.
I'm using bullMQ and I have a nodeJS project for GAE, I want to deploy it, but I saw that Google Memorystorage only supports Redis until version 4.0.14, and BullMQ needs Redis 5 at least.
Then I have 2 options:
1. Go down to older version of bullMQ -> bullJS
2. Create a VM with REDIS 5 while Google release official support for it in memorystorage.
That's why I need to know the official date to take a decition.
Thanks in advances.
Any news when Tensorflow 2 will be supported on Google Cloud AI platform?
According to the list, 1.15 is the last version to be supported: https://cloud.google.com/ml-engine/docs/runtime-version-list
we will support TF 2.1 officially in early Feb due to large corresponding changes on service. Thank you for your patience!
Add a dependency tensorflow-gpu==2.0 to setup.py file to train with Tensorflow 2.0 in AI Platform run-time version 1.15. Tensorflow 2.1 can't use GPUs due to mismatch in CUDA libraries, but you can train with CPUs. Be careful that other dependencies don't overwrite tensorflow-gpu. Disclaimer: I trained just one job this way, and this is a really hacky solution.
Tensorflow 2.1 runtime version is available as of March 9th
https://cloud.google.com/ai-platform/training/docs/runtime-version-list
The Google Compute Engine announcement mentions support for RHEL, SUSE, and FreeBSD. On VM creation only Debian and CentOS are available. Is FreeBSD support still being worked on or do I need to create my own disk image to start with?
FreeBSD is now supported by the service, but images are not provided by Google. Paul Rashidi has posted detailed steps for creating a FreeBSD image.
Later in the same thread, Dave Cottlehuber shares a tool he created to make installation easier.
For RHEL and SUSE, there is a signup link in the Premium Operating Systems documentation.
update: On June 9th, we published a video walking through the details of How to build a custom image for Compute Engine.
I've been working on a script to build images for FreeBSD on Google Compute Engine, see:
https://plus.google.com/112202779615695172291/posts/eYajb8JKerY
for more details.
Anther option for building images can be found here:
https://github.com/daveish/freebsd-gce-tools
The documentation for CloudFoundry indicates that Node.js version 0.8.2 is supported. However, when I run "vmc runtimes" against my local micro edition, it only lists node and node06 (not node08)
I'm running 0.8.2 locally on my box -- how can I upgrade Micro edition so that it also has 0.8.2 installed?
Micro Cloud Foundry 1.2 was released before Node.js 0.8.2 support was added. MCF currently cannot be upgraded to support it. However, a new MCF version is planned for the very near future which will bring parity to all the feature on CloudFoundry.com. We also plan a faster release cadence of MCF so it doesn't fall behind on features.
It's not completely trivial to patch MCF 1.2 to add node 0.8, you'd need to install the relevant packages as well as add information to the Cloud Foundry manifest files to enable it to advertise the node08 runtime.
However, the next Micro Cloud Foundry release should be available pretty soon so if you can hold on just a little longer, we should have some good news for you :-)
Out of interest, what application are you looking to build / run that requires 0.8.x?
Micro Cloud Foundry has just been updated to be in sync with the codebase on github so it now supports Node.js 0.8.2. Read the announcement here: http://blog.cloudfoundry.com/2012/11/08/new-release-of-micro-cloud-foundry/