Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-26 23:08:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/dotnet-sdk] Release 10.0.200-debian-12-r0 (#91478)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-03-10 20:24:18 +01:00
committed by GitHub
parent 5c9414b5e8
commit 419c53dd42
2 changed files with 14 additions and 86 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
bitnami/dotnet-sdk/10/debian-12/Dockerfile
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:21Z" \
org.opencontainers.image.created="2026-03-10T18:58:37Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/dotnet-sdk/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/dotnet-sdk" \
org.opencontainers.image.title="dotnet-sdk" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="10.0.103"
org.opencontainers.image.version="10.0.200"
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-sdk-10.0.103-0-linux-${OS_ARCH}-debian-12" \
"dotnet-sdk-10.0.200-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-sdk/postunpack.sh
ENV APP_VERSION="10.0.103" \
ENV APP_VERSION="10.0.200" \
BITNAMI_APP_NAME="dotnet-sdk" \
DOTNET_CLI_HOME="/app" \
DOTNET_ROOT="/opt/bitnami/dotnet-sdk/bin" \
IMAGE_REVISION="1" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/dotnet-sdk/bin:$PATH"
WORKDIR /app

90
bitnami/dotnet-sdk/README.md
View File

@@ -1,7 +1,5 @@
# Bitnami Secure Image for .NET SDK
## What is .NET SDK?
> .NET SDK is the software development kit for the ASP.NET Core framework.
[Overview of .NET SDK](https://dotnet.microsoft.com/apps/aspnet)
@@ -56,53 +54,31 @@ 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-sdk:latest
```
You can also do this with a minor change to the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/dotnet-sdk/docker-compose.yml) file present in this repository:
```yaml
dotnet-sdk:
...
volumes:
- /path/to/dotnet-persistence:/app
...
```
## 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
## Configuration
#### Step 1: Create a network
The following section describes how to configure the application
```console
docker network create dotnet-network --driver bridge
```
### FIPS configuration in Bitnami Secure Images
#### Step 2: Launch the .NET SDK container within your network
The Bitnami .NET SDK 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:
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-sdk: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.
- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
## Logging
@@ -114,54 +90,6 @@ docker logs dotnet-sdk
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 .NET SDK, 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-sdk:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the command
```console
docker stop dotnet-sdk
```
#### Step 3: Remove the currently running container
```console
docker rm -v dotnet-sdk
```
#### Step 4: Run the new image
Re-create your container from the new image.
```console
docker run --name dotnet-sdk bitnami/dotnet-sdk: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).
## Configuration
### FIPS configuration in Bitnami Secure Images
The Bitnami .NET SDK 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:
- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
## License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.