Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-02-13 16:07:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/gitea] Release 1.18.3-debian-11-r9 (#24222)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-02-17 18:13:18 +01:00
committed by GitHub
parent effbdfe651
commit 038d1210d9
3 changed files with 20 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
bitnami/gitea/1/debian-11/Dockerfile
View File

@@ -2,11 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-02-17T14:28:34Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="1.18.3-debian-11-r8" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/gitea" \
org.opencontainers.image.ref.name="1.18.3-debian-11-r9" \
org.opencontainers.image.title="gitea" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="1.18.3"
@@ -22,11 +22,11 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages acl ca-certificates curl git procps
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"wait-for-port-1.0.6-0-linux-${OS_ARCH}-debian-11" \
"render-template-1.0.5-0-linux-${OS_ARCH}-debian-11" \
"ini-file-1.4.5-0-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"gitea-1.18.3-1-linux-${OS_ARCH}-debian-11" \
"wait-for-port-1.0.6-1-linux-${OS_ARCH}-debian-11" \
"render-template-1.0.5-1-linux-${OS_ARCH}-debian-11" \
"ini-file-1.4.5-1-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
"gitea-1.18.3-2-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

20
bitnami/gitea/1/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@@ -1,37 +1,37 @@
{
"gitea": {
"arch": "amd64",
"digest": "0e10b1e90673b286941e63238cff096ce2c7c31d86841f6ce9c8bc92e20d2e4d",
"digest": "9e18360c0ec27ec80bb3a9e10fa2905fd4d9413c8ec3cf2d87552b2e0d57ca29",
"distro": "debian-11",
"type": "NAMI",
"version": "1.18.3-1"
"version": "1.18.3-2"
},
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"ini-file": {
"arch": "amd64",
"digest": "d82fb302437effeec0d20f104b35304c46cf295bb3af56ab00d69ad4ffd39eb0",
"digest": "75d5f74f62ca3a476e5ffc01715b197ba18c3b45a85b18fb61cc68e998616119",
"distro": "debian-11",
"type": "NAMI",
"version": "1.4.5-0"
"version": "1.4.5-1"
},
"render-template": {
"arch": "amd64",
"digest": "57c1d857acbb187fcb98f4ba26d138af9d866f59ad38dd443a75c0a6422de994",
"digest": "185e277977366ec222d2bde1a395ffa138ce1a9d3bdf1df20c3e49e8b8f9c68b",
"distro": "debian-11",
"type": "NAMI",
"version": "1.0.5-0"
"version": "1.0.5-1"
},
"wait-for-port": {
"arch": "amd64",
"digest": "f9199cd66b92fef328ecfbc5ffbc8f14be33257a4e34b8c6ba35a730c5a2f59d",
"digest": "be7c393d598ddf16d1c3c008a67b87879e48aca62071a208583390f2b41e6744",
"distro": "debian-11",
"type": "NAMI",
"version": "1.0.6-0"
"version": "1.0.6-1"
}
}

2
bitnami/gitea/README.md
View File

@@ -126,7 +126,7 @@ docker run -it --rm \
bitnami/gitea:latest gitea-client --host gitea-server
```
### Using Docker Compose
### Using a Docker Compose file
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `my-network`. In this example we assume that you want to connect to the Gitea server from your own custom application image which is identified in the following snippet by the service name `myapp`.