[bitnami/dotnet] Release 10.0.4-debian-12-r0 (#91479)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-03-10 20:32:49 +01:00 committed by GitHub
parent 419c53dd42
commit 2ec3aae51e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 11 additions and 83 deletions

View File

@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-02-19T01:07:35Z" \
org.opencontainers.image.created="2026-03-10T18:48:59Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/dotnet/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/dotnet" \
org.opencontainers.image.title="dotnet" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="10.0.3"
org.opencontainers.image.version="10.0.4"
ENV HOME="/app" \
OS_ARCH="${TARGETARCH:-amd64}" \
@ -28,7 +28,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"dotnet-10.0.3-0-linux-${OS_ARCH}-debian-12" \
"dotnet-10.0.4-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@ -48,11 +48,11 @@ RUN sed -i 's/^PASS_MAX_DAYS.*/PASS_MAX_DAYS 90/' /etc/login.defs && \
COPY rootfs /
RUN /opt/bitnami/scripts/dotnet/postunpack.sh
ENV APP_VERSION="10.0.3" \
ENV APP_VERSION="10.0.4" \
BITNAMI_APP_NAME="dotnet" \
DOTNET_CLI_HOME="/app" \
DOTNET_ROOT="/opt/bitnami/dotnet/bin" \
IMAGE_REVISION="1" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/dotnet/bin:$PATH"
WORKDIR /app

View File

@ -1,7 +1,5 @@
# Bitnami Secure Image for .NET
## What is .NET?
> .NET is an open-source server-side framework to build applications and services.
[Overview of .NET](https://dotnet.microsoft.com/)
@ -56,56 +54,26 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## Using `docker-compose.yaml`
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes.
## Persisting your application
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the `/bitnami` path. If the mounted directory is empty, it will be initialized on the first run.
```console
docker run \
-v /path/to/dotnet-persistence:/bitnami \
bitnami/dotnet:latest
```
You can also do this with a minor change to the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/dotnet/docker-compose.yml) file present in this repository:
```yaml
dotnet:
...
volumes:
- /path/to/dotnet-persistence:/bitnami
...
```
## Connecting to other containers
Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa.
Containers attached to the same network can communicate with each other using the container name as the hostname.
### Using the Command Line
#### Step 1: Create a network
```console
docker network create dotnet-network --driver bridge
```
#### Step 2: Launch the Dotnet container within your network
Use the `--network .NETWORK>` argument to the `docker run` command to attach the container to the `dotnet-network` network.
```console
docker run --name dotnet-node1 --network dotnet-network bitnami/dotnet:latest
```
#### Step 3: Run another containers
We can launch another containers using the same flag (`--network.NETWORK`) in the `docker run` command. If you also set a name to your container, you will be able to use it as hostname in your network.
## Configuration
The following section describes how to configure the application
### FIPS configuration in Bitnami Secure Images
The Bitnami .NET Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
@ -122,46 +90,6 @@ docker logs dotnet
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Maintenance
### Upgrade this image
Bitnami provides up-to-date versions of Dotnet, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
#### Step 1: Get the updated image
```console
docker pull bitnami/dotnet:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the command
```console
docker stop dotnet
```
#### Step 3: Remove the currently running container
```console
docker rm -v dotnet
```
#### Step 4: Run the new image
Re-create your container from the new image.
```console
docker run --name dotnet bitnami/dotnet:latest
```
## Using `docker-compose.yaml`
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes.
If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
## License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.