Add a document on installing the VMware VDDK on containers #1706
Conversation
|
|
||
| 3. Copy the tar file into the container-assets directory. For Example: | ||
| ```bash | ||
| $ cp ~/Downloads/VMware-vix-disklib-7.0.1-16860560.x86_64.tar.gz /tmp/vddk_container/container-assets |
There was a problem hiding this comment.
Should this be a generic version value and we point to another document describing what versions of vddk we support and against which versions of vsphere? cc @agrare
| ################################################################################ | ||
|
|
||
| ### IMPORTANT: Modify the following image and tag as necessary to reflect the version that you're running | ||
| FROM docker.io/manageiq/manageiq-base-worker:latest |
There was a problem hiding this comment.
Should this point to a non-existing image and tag so they can't forget to update this value?
| ```bash | ||
| $ cd /tmp/vddk_container/ | ||
| $ docker build . -t your_registry.example.com/namespace/manageiq-base-worker:latest_vddk | ||
| $ docker push your_registry.example.com/namespace/manageiq-base-worker:latest_vddk |
There was a problem hiding this comment.
I like this example registry, image and tag. They can't forget to update it and the it's very clear what needs to be done here.
| baseWorkerImage: your_registry.example.com/namespace/manageiq-base-worker:latest_vddk | ||
| ``` | ||
|
|
||
| The operator will now update the orchestrator and worker deployments to reflect this change. |
There was a problem hiding this comment.
What do they need to do if we release a new image? Ideally, it's just changing the
FROM ... and updating the revision of their image tag they build and push, right?
There was a problem hiding this comment.
Yes, they will need to rebuild anytime we update the image.
|
Checked commit bdunne@7271699 with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint |
Based on:
Fixes: #1479