[bitnami/kuberay-operator] Release 1.0.0-debian-11-r5 (#55042)
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
parent
3a84d51c87
commit
a553a1721c
|
|
@ -7,10 +7,10 @@ ARG TARGETARCH
|
|||
|
||||
LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
|
||||
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
|
||||
org.opencontainers.image.created="2024-01-10T14:49:04Z" \
|
||||
org.opencontainers.image.created="2024-01-19T22:58:11Z" \
|
||||
org.opencontainers.image.description="Application packaged by VMware, Inc" \
|
||||
org.opencontainers.image.licenses="Apache-2.0" \
|
||||
org.opencontainers.image.ref.name="1.0.0-debian-11-r4" \
|
||||
org.opencontainers.image.ref.name="1.0.0-debian-11-r5" \
|
||||
org.opencontainers.image.title="kuberay" \
|
||||
org.opencontainers.image.vendor="VMware, Inc." \
|
||||
org.opencontainers.image.version="1.0.0"
|
||||
|
|
@ -41,6 +41,7 @@ RUN apt-get autoremove --purge -y curl && \
|
|||
apt-get update && apt-get upgrade -y && \
|
||||
apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives
|
||||
RUN useradd -r -u 1001 -g root kuberay
|
||||
RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
|
||||
|
||||
ENV APP_VERSION="1.0.0" \
|
||||
BITNAMI_APP_NAME="kuberay" \
|
||||
|
|
|
|||
|
|
@ -1,8 +0,0 @@
|
|||
# Copyright VMware, Inc.
|
||||
# SPDX-License-Identifier: APACHE-2.0
|
||||
|
||||
version: '2'
|
||||
|
||||
services:
|
||||
kuberay-operator:
|
||||
image: docker.io/bitnami/kuberay-operator:1
|
||||
|
|
@ -13,13 +13,6 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
|
|||
docker run -it --name kuberay-operator bitnami/kuberay-operator
|
||||
```
|
||||
|
||||
### Docker Compose
|
||||
|
||||
```console
|
||||
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/kuberay-operator/docker-compose.yml > docker-compose.yml
|
||||
docker-compose up -d
|
||||
```
|
||||
|
||||
## Why use Bitnami Images?
|
||||
|
||||
- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
|
||||
|
|
@ -73,20 +66,12 @@ Bitnami provides up-to-date versions of KubeRay, including security patches, soo
|
|||
docker pull bitnami/kuberay-operator:latest
|
||||
```
|
||||
|
||||
or if you're using Docker Compose, update the value of the image property to `bitnami/kuberay-operator:latest`.
|
||||
|
||||
#### Step 2: Remove the currently running container
|
||||
|
||||
```console
|
||||
docker rm -v kuberay-operator
|
||||
```
|
||||
|
||||
or using Docker Compose:
|
||||
|
||||
```console
|
||||
docker-compose rm -v kuberay-operator
|
||||
```
|
||||
|
||||
#### Step 3: Run the new image
|
||||
|
||||
Re-create your container from the new image.
|
||||
|
|
@ -95,12 +80,6 @@ Re-create your container from the new image.
|
|||
docker run --name kuberay-operator bitnami/kuberay-operator:latest
|
||||
```
|
||||
|
||||
or using Docker Compose:
|
||||
|
||||
```console
|
||||
docker-compose up kuberay-operator
|
||||
```
|
||||
|
||||
## Configuration
|
||||
|
||||
### Running commands
|
||||
|
|
@ -113,6 +92,12 @@ docker run --rm --name kuberay-operator bitnami/kuberay-operator:latest --help
|
|||
|
||||
Check the [official KubeRay documentation](https://ray.io) for more information about how to use KubeRay.
|
||||
|
||||
## Notable Changes
|
||||
|
||||
### Starting January 16, 2024
|
||||
|
||||
* The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kuberay).
|
||||
|
||||
## Contributing
|
||||
|
||||
We'd love for you to contribute to this Docker image. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues) or submitting a [pull request](https://github.com/bitnami/containers/pulls) with your contribution.
|
||||
|
|
|
|||
Loading…
Reference in New Issue