init: update README.md with alternative locations of parent image

This commit is contained in:
Paul Monday 2021-08-25 17:08:41 -06:00
parent ffa40275f2
commit ef35bf1a6d

View File

@ -19,7 +19,6 @@ ZFS Storage Appiance (or simulator). The management and data path
can be the same address. can be the same address.
* A suitable container image build environment. The Makefile currently uses docker * A suitable container image build environment. The Makefile currently uses docker
but with minor updates to release-tools/build.make, podman should also be usable. but with minor updates to release-tools/build.make, podman should also be usable.
* An account for use with [container-registry.oracle.com](https://container-registry.oracle.com/) image registry.
## Unsupported Functionality ## Unsupported Functionality
ZFS Storage Appliance CSI driver does not support the following functionality: ZFS Storage Appliance CSI driver does not support the following functionality:
@ -36,16 +35,16 @@ make build
Depending on your golang installation, there may be dependencies identified by the build, install Depending on your golang installation, there may be dependencies identified by the build, install
these and retry the build. these and retry the build.
Prior to building the container image, docker login to container-registry.oracle.com so the The parent image for the container is container-registry.oracle.com/os/oraclelinux:7-slim, refer
parent image container-registry.oracle.com/os/oraclelinux:7-slim can be retrieved. There may to [container-registry.oracle.com](https://container-registry.oracle.com/) for more information.
be license terms to accept at the web entry to the container registry: The parent image can also be obtained from ghcr.io/oracle/oraclelinux and docker.io/library/oraclelinux.
[container-registry.oracle.com](https://container-registry.oracle.com/).
Once you are logged in you can make the container with the following: To build the container:
``` ```
make container make container
``` ```
Tag and push the resulting container image to a container registry. Tag and push the resulting container image to a container registry available to the
Kubernetes cluster where it will be deployed.
## Installation ## Installation