The bitnami-compat from zcube

[CI/CD] Update submodules on a cron job

Hi 👋

Is it feasible to periodically bring the submodules up to date using GitHub Actions (example)? Such that security patches etc get published on push automatically?

Alternatively, if you don't want a cron job pushing to master, you could have the cron job open a PR, and have automerge push it to master once checks finish (e.g. images still build successfully).

Wordpress Support

Does wordpress-nginx equivalent to bitnami/wordpress?

Thanks for amazing job!

Zookeeper suppport

Anyway to support zoo keeper that can run with the already supported kafka chart?

mongodb 4.4.15 - missing mongosh

Thanks for resolving #37. I get the following errors in a fresh deployment of the bitnami/mongodb chart, version 11.1.10:

mongodb 16:09:08.84 
mongodb 16:09:08.93 Welcome to the Bitnami mongodb container
mongodb 16:09:08.94 Subscribe to project updates by watching https://github.com/bitnami/containers
mongodb 16:09:09.02 Submit issues and feature requests at https://github.com/bitnami/containers/issues
mongodb 16:09:09.03 
mongodb 16:09:09.04 INFO  ==> ** Starting MongoDB setup **
mongodb 16:09:09.43 INFO  ==> Validating settings in MONGODB_* env vars...
mongodb 16:09:10.47 INFO  ==> Initializing MongoDB...
mongodb 16:09:10.95 INFO  ==> Deploying MongoDB from scratch...
/opt/bitnami/scripts/libmongodb.sh: line 1593: /opt/bitnami/mongodb/bin/mongosh: No such file or directory
/opt/bitnami/scripts/libmongodb.sh: line 1593: /opt/bitnami/mongodb/bin/mongosh: No such file or directory
/opt/bitnami/scripts/libmongodb.sh: line 1593: /opt/bitnami/mongodb/bin/mongosh: No such file or directory

I originally used the latest chart version (13.1.7) but it had a similar issue where the liveness and readiness probes were trying to call mongosh, now it's limited to when the db is first initialized.

From what I can tell, 4.4 migrated to using mongosh instead of mongo here: https://github.com/bitnami/bitnami-docker-mongodb/commit/3a84d6636829d5d940f57e7bafdd72d253c876e4

I think something easy that might work for me is just to re-publish version 4.4.12, that should have the old code that calls mongo but it would be nice to get the latest 4.4 image fixed. I'm also happy to create my own docker image that patches these scripts if this isn't something you want to support.

In case you're wondering, I need to use version 4 instead of 5+ of mongo because they require ARMv8.2-A or later. I'm deploying this on a Raspberry Pi 4B which is based on ARMv8.0-A

Thank you!

Connection problems with keycloak & postgress

Hello

on my pi 4 (4GB,ubuntu,microk8s) i try to install the bitnami helmchart for keycloak with the zcube images. The same chart on my windows pc with the original images and without an values.yaml works without problems.

It seems with the zcube images keycloak has problems to reach the DB. It is possible, that there is a module missing, as it is said in the first error Module for driver [org.postgresql.jdbc] or one of it dependencies is missing: [org.postgresql.jdbc]. Does the convertion delete some modules? I also found out, that there seems to be some problems with ENV vars bitnami/charts#7305 (comment), but i dont know if the issue also affect the keycloak chart, and if this is even the problem.

If you have a hint, how to check that, or how to set the ENVs manually via the helmchart, i like to have some assistance.

values.yaml

image:
  registry: ghcr.io
  repository: zcube/bitnami-compat/keycloak
  tag: 16.1.1

postgresql:
  image:
    registry: ghcr.io
    repository: zcube/bitnami-compat/postgresql
    tag: 11.14.0

kubectl create namespace keycloak
kubectl apply -f persistentvolume.yml
helm -n keycloak install keycloak bitnami/keycloak -f values.yaml

kubectl -n keycloak logs -f keycloak-postgresql-0 > db.txt db.txt

...
postgresql 14:46:56.55 INFO  ==> Creating user bn_keycloak
postgresql 14:46:56.62 INFO  ==> Granting access to "bn_keycloak" to the database "bitnami_keycloak"
postgresql 14:46:56.76 INFO  ==> Setting ownership for the 'public' schema database "bitnami_keycloak" to "bn_keycloak"
...
2022-02-16 14:46:57.910 GMT [1] LOG:  database system is ready to accept connections
2022-02-16 14:46:58.524 GMT [176] LOG:  incomplete startup packet
2022-02-16 14:49:50.649 GMT [427] LOG:  incomplete startup packet

kubectl -n keycloak logs -f keycloak-0 > keycloak_first_start.txt keycloak_first_start.txt

...
keycloak 14:46:37.86 INFO  ==> Trying to connect to PostgreSQL server keycloak-postgresql...
timeout reached before the port went into state "inuse"
keycloak 14:46:58.53 INFO  ==> Found PostgreSQL server listening at keycloak-postgresql:5432
...
14:49:22,260 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("jdbc-driver" => "postgresql")
]) - failure description: "WFLYJCA0115: Module for driver [org.postgresql.jdbc] or one of it dependencies is missing: [org.postgresql.jdbc]"
...
14:49:45,789 FATAL [org.keycloak.services] (ServerService Thread Pool -- 66) Error during startup: java.lang.RuntimeException: Failed to connect to database
...
Caused by: javax.naming.NameNotFoundException: datasources/KeycloakDS [Root exception is java.lang.IllegalStateException]
...
Caused by: java.lang.IllegalStateException

kubectl -n keycloak logs -f keycloak-0 > keycloak_second_start.txt keycloak_second_start.txt

keycloak 14:49:50.62 INFO  ==> Trying to connect to PostgreSQL server keycloak-postgresql...
keycloak 14:49:50.65 INFO  ==> Found PostgreSQL server listening at keycloak-postgresql:5432
...
(same as first start)

Contour / Envoy

They run pretty well on ARM, but they are the last images I'm missing for now

galera support

Would galera docker image: https://hub.docker.com/r/bitnami/mariadb-galera work with bitnami-compat?
If so is it possible to add the support for this image?

MongoDB support

Hi, I was wondering about building the image for MongoDB 4.4 but I'm not sure what to do on step "3. Write build scripts"
Bitnami uses official MongoDB images and I'm not sure if I have to write any build script.
Thanks

Limit the versions that get generated, built and published

At the moment if you want to build just one app it still builds and push all versions of that app. It would be nice to be able to only build and push one version e.g. Postgresql 14 only.

Current Status

Supports 32 out of 100 charts
- Accepted 3 Pull Requests for patches
- Accepted 0 Pull Requests for new images
- The charts I(zcube) wants are already supported.
- Supported approximately 15 additional chart support requests.
- In the case of general apps, it is excluded because it takes a long time to produce patches.
Component patch and App patch must be separated
- There are cases where components are used as apps, so there are issues with management.
Not production Ready
- 1 main developer -> a private repository that is open source -> not trusted
- Some users also require a CVE check.
- DCT needed?
- main branch protection
Test
- https://github.com/ZCube/bitnami-compat-test
Support image version update every Friday
- Breaking changes propagated from external repositories. -> Maintenance time required per week, not production ready
- In the case of apt packages, there are cases where the actual version does not match.
My(ZCube's) status
- busy with work
  - minimum maintenance stance
  - no ETA for test and release process

Postgresql image (15.1.0-debian-11-r19)

Trying to use:

image:
  registry: ghcr.io  # required for arm64
  repository: zcube/bitnami-compat/postgresql  # required for arm64
  tag: 15.1.0-debian-11-r19

But getting Error response from daemon: manifest unknown.

Helm charts

Hi! It's been a while. I wanted to let you know that I am going to be working on some helm charts for this repository here: https://github.com/RedstoneWizard08/bitnami-compat-charts. I might create a PR to merge them into this repository once they're done as well. Thank you so much for making this possible!

Memcached support

It would be nice to have that too

Build Keycloak v19

There is a new v19 Keycloak folder which is not part of the build process

Add other charts to the test.

Test

If the image is not ready, it should be tested with the official version.

Charts

Encountered an Error when building: "failed to solve: rpc error: code = Unknown desc = docker.io/bitnami/minideb:bullseye: failed to do request"

thanks in advance sir

fluentd support

I would like to have fluentd images as well.

Bitnami Kubectl Image

Request to add the Kubectl image: https://github.com/bitnami/bitnami-docker-kubectl

Needed for a thing:

235 | ...
236 |   # enabled cronjob to restart the proxy deployment
237 |   restarter:
238 |     enabled: false
239 |     schedule: '0 0 * * 0'
240 |     image: bitnami/kubectl:latest
241 |     targets:
242 |     - name: proxy
243 |       kind: deployment
244 |     - name: registry-facade
245 |       kind: daemonset
246 |     - name: ws-proxy
247 |       kind: deployment
248 | ...

bitnami-compat/rabbitmq:3.9.23 failing to start up on `linux/amd64` macOS

I have confirmed that this issue is not present in 3.9.22 by switching versions and starting them up repeatedly

I have it defined in a docker compose file like this:

  rabbitmq:
    # https://github.com/zcube/bitnami-compat
    image: ghcr.io/zcube/bitnami-compat/rabbitmq:3.9.23
    volumes:
      - local_rabbitmq_data:/bitnami
    ports:
      - "15672:15672"

and when bringing it up it fails with these logs:

-rabbitmq-1  | rabbitmq 20:15:18.71 
-rabbitmq-1  | rabbitmq 20:15:18.71 Welcome to the Bitnami rabbitmq container
-rabbitmq-1  | rabbitmq 20:15:18.71 Subscribe to project updates by watching https://github.com/bitnami/containers
-rabbitmq-1  | rabbitmq 20:15:18.71 Submit issues and feature requests at https://github.com/bitnami/containers/issues
-rabbitmq-1  | rabbitmq 20:15:18.71 
-rabbitmq-1  | rabbitmq 20:15:18.72 INFO  ==> ** Starting RabbitMQ setup **
-rabbitmq-1  | rabbitmq 20:15:18.73 INFO  ==> Validating settings in RABBITMQ_* env vars..
-rabbitmq-1  | rabbitmq 20:15:18.74 INFO  ==> Initializing RabbitMQ...
-rabbitmq-1  | rabbitmq 20:15:18.75 INFO  ==> Generating random cookie
-rabbitmq-1  | rabbitmq 20:15:18.77 INFO  ==> Starting RabbitMQ in background...
-rabbitmq-1  | rabbitmq 20:17:00.86 ERROR ==> Couldn't start RabbitMQ in background.
-rabbitmq-1 exited with code 1

Exec format error in etcd image

/opt/bitnami/scripts/etcd/run.sh: line 38: /opt/bitnami/etcd/bin/etcd: cannot execute binary file: Exec format error

docker pull ghcr.io/zcube/bitnami-compat/etcd:3.4.19-debian-11-r15@sha256:cd24be04de0b05d387ce2daf8292ca7005e40397baad733e30e2542eaeeb50d8

image contains x86 executable instead of arm executable:

$ file ~/etcd 
/home/rob/etcd: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=FSBJvFHmr1ACg8cTm_55/XpAKBUDXx_P7l65LhXfZ/AjC-86e9h5c96McaiK7A/dmLNcGeVsI7V9bw23l9q, stripped

Add Vulnerability Scanner and Publish Results

Feature Description

Todo

Add triviy scanner result to branch in json format. ( example branch : trivy/nginx file : trivy_result.json )
Convert Json to markdown format.
Publish using https://github.com/dbsystel/trivy-vulnerability-explorer.

Reference

https://github.com/dbsystel/trivy-vulnerability-explorer

Odoo Support

Could you consider Odoo chart support? I have tried a custom image with arm support but some path doesn't match with the official bitnami chart values.

Thanks for amazing job btw.

[FR] Discourse with arm compatibilty?

Is there a plan to add discourse with arm?

postgresql images broken?

Hi, it seems the postgresql images are currently broken? My database pod (thankfully a test deployment) is crashlooping.
It worked before the recent image update.

Here's my pod; as you can see it was deployed from the bitnami helm chart:

kubectl --kubeconfig=/home/michael/.kube/k3s -n testcloud describe pod testcloud-postgresql-0 
Name:         testcloud-postgresql-0
Namespace:    testcloud
Priority:     0
Node:         server/10.0.1.147
Start Time:   Tue, 22 Feb 2022 18:35:30 +0100
Labels:       app.kubernetes.io/component=primary
              app.kubernetes.io/instance=testcloud
              app.kubernetes.io/managed-by=Helm
              app.kubernetes.io/name=postgresql
              controller-revision-hash=testcloud-postgresql-cd8845ff9
              helm.sh/chart=postgresql-10.13.11
              role=primary
              statefulset.kubernetes.io/pod-name=testcloud-postgresql-0
Annotations:  <none>
Status:       Running
IP:           10.42.0.127
IPs:
  IP:           10.42.0.127
Controlled By:  StatefulSet/testcloud-postgresql
Containers:
  testcloud-postgresql:
    Container ID:   containerd://c07972b9496c7028b25ebd03b17cf04fb5bae999c792b87f4014406c9b695515
    Image:          ghcr.io/ghcr.io/zcube/bitnami-compat/postgresql:14-debian-10
    Image ID:       ghcr.io/ghcr.io/zcube/bitnami-compat/postgresql@sha256:9b110076bc68c6806e308001b7db618f4047b73b82047065dd0ca6ac15ac3097
    Port:           5432/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 22 Feb 2022 21:51:25 +0100
      Finished:     Tue, 22 Feb 2022 21:51:26 +0100
    Ready:          False
    Restart Count:  43
    Requests:
      cpu:      250m
      memory:   256Mi
    Liveness:   exec [/bin/sh -c exec pg_isready -U "nextcloud" -d "dbname=nextcloud" -h 127.0.0.1 -p 5432] delay=30s timeout=5s period=10s #success=1 #failure=6
    Readiness:  exec [/bin/sh -c -e exec pg_isready -U "nextcloud" -d "dbname=nextcloud" -h 127.0.0.1 -p 5432
] delay=5s timeout=5s period=10s #success=1 #failure=6
    Environment:
      BITNAMI_DEBUG:                        false
      POSTGRESQL_PORT_NUMBER:               5432
      POSTGRESQL_VOLUME_DIR:                /bitnami/postgresql
      PGDATA:                               /bitnami/postgresql/data
      POSTGRES_POSTGRES_PASSWORD:           <set to the key 'postgresql-postgres-password' in secret 'testcloud-postgresql'>  Optional: false
      POSTGRES_USER:                        nextcloud
      POSTGRES_PASSWORD:                    <set to the key 'postgresql-password' in secret 'testcloud-postgresql'>  Optional: false
      POSTGRES_DB:                          nextcloud
      POSTGRESQL_ENABLE_LDAP:               no
      POSTGRESQL_ENABLE_TLS:                no
      POSTGRESQL_LOG_HOSTNAME:              false
      POSTGRESQL_LOG_CONNECTIONS:           false
      POSTGRESQL_LOG_DISCONNECTIONS:        false
      POSTGRESQL_PGAUDIT_LOG_CATALOG:       off
      POSTGRESQL_CLIENT_MIN_MESSAGES:       error
      POSTGRESQL_SHARED_PRELOAD_LIBRARIES:  pgaudit
    Mounts:
      /bitnami/postgresql from data (rw)
      /dev/shm from dshm (rw)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  data-testcloud-postgresql-0
    ReadOnly:   false
  dshm:
    Type:        EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:      Memory
    SizeLimit:   <unset>
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason   Age                    From     Message
  ----     ------   ----                   ----     -------
  Normal   Pulled   11m (x42 over 3h16m)   kubelet  Container image "ghcr.io/ghcr.io/zcube/bitnami-compat/postgresql:14-debian-10" already present on machine
  Warning  BackOff  92s (x962 over 3h16m)  kubelet  Back-off restarting failed container

Here's the log from the container startup:

postgresql 20:51:25.94 
postgresql 20:51:25.94 Welcome to the Bitnami postgresql container
postgresql 20:51:25.95 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql
postgresql 20:51:25.95 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql/issues
postgresql 20:51:25.96 
postgresql 20:51:25.98 INFO  ==> ** Starting PostgreSQL setup **
postgresql 20:51:26.00 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql 20:51:26.01 INFO  ==> Loading custom pre-init scripts...
postgresql 20:51:26.02 INFO  ==> Initializing PostgreSQL database...
postgresql 20:51:26.06 INFO  ==> pg_hba.conf file not detected. Generating it...
postgresql 20:51:26.06 INFO  ==> Generating local authentication configuration
postgresql 20:51:26.07 INFO  ==> Deploying PostgreSQL with persisted data...
postgresql 20:51:26.10 INFO  ==> Configuring replication parameters
/opt/bitnami/scripts/libpostgresql.sh: line 374: ((: 14
14: syntax error in expression (error token is "14")
postgresql 20:51:26.13 INFO  ==> Configuring fsync
postgresql 20:51:26.14 INFO  ==> Configuring synchronous_replication
postgresql 20:51:26.17 INFO  ==> Loading custom scripts...
postgresql 20:51:26.18 INFO  ==> Enabling remote connections
postgresql 20:51:26.20 INFO  ==> ** PostgreSQL setup finished! **

postgresql 20:51:26.22 INFO  ==> ** Starting PostgreSQL **
2022-02-22 20:51:26.277 GMT [1] LOG:  unrecognized configuration parameter "wal_keep_segments" in file "/opt/bitnami/postgresql/conf/postgresql.conf" line 800
2022-02-22 20:51:26.277 GMT [1] FATAL:  configuration file "/opt/bitnami/postgresql/conf/postgresql.conf" contains errors

The error message seems to lead to this function in the init script that tries to get the major version number: https://github.com/bitnami/bitnami-docker-postgresql/blob/42e404613f3e0c4120b0d4aea24d1d0fdae15eb3/14/debian-10/rootfs/opt/bitnami/scripts/libpostgresql.sh#L1001

When I manually execute the statement in a test pod I get the version number, but twice. Could this be the problem; and if so is it specific to your build?

root@pgdebug:/# psql --version | grep -oE "[0-9]+\.[0-9]+" | grep -oE "^[0-9]+"
14
14
root@pgdebug:/# psql --version
psql (PostgreSQL) 14.2 (Debian 14.2-1.pgdg100+1)

Also, the version number in the pod is 14.2 but on the ghcr page it clams to be 14.1?

Since I can't attach the pod definition, here's the test pod yaml file:

apiVersion: v1
kind: Pod
metadata:
  name: pgdebug
  namespace: nextcloud
spec:
  containers:
  - image: ghcr.io/zcube/bitnami-compat/postgresql:14-debian-10
    imagePullPolicy: Always
    name: postgres
    env:
    - name: BITNAMI_DEBUG
      value: "true"
    command: 
    - sleep
    args:
    - "3600"
    securityContext:
      runAsUser: 0

can't pull image for mongodb 4.4.15

Really appreciate the work you're doing here.

None of the mongodb v4 images are being successfully pulled, I keep getting a manifest unknown error.

# successful
> docker pull ghcr.io/zcube/bitnami-compat/mongodb:6.0.2 

# unsuccessful
> docker pull ghcr.io/zcube/bitnami-compat/mongodb:4.4.15
4.4.15: Pulling from zcube/bitnami-compat/mongodb
manifest unknown

Any idea on what's going on? Thanks

Add test step to CI/CD

Feature Description

The biggest issue currently keeping us from deploying as Product Ready is testing.

The intended use of images from this repository is Bitnami charts, so it's best to do the tests included in Bitnami charts.

Step 1. Create testing workflow

Create test environment by k3s + github actions.
Create values.yaml for test
- Change images to use bitnami-compat
- Some extra configuration
Add CI/CD tests for minio chart.
- goss
- cypress
Set up a self-hosted environment that supports Arm on Github Actions.

Reference:

https://gist.github.com/ZCube/e1c14ff029d153210feaa1a3db9456c1 (Basic Github Workflow for testing charts)
https://github.com/debianmaster/actions-k3s
https://github.com/bitnami/charts/blob/main/.vib/nginx/goss
https://github.com/bitnami/charts/blob/main/.vib/nginx/cypress

missing rabbitmq:3.9.13-debian-10 image

I can no longer pull the ghcr.io/zcube/rabbitmq:3.9.13-debian-10-r0 image or any of the other 3.9 related images.

Discourse marked as supported yet not built?

Discourse is marked as supported by the charts but it does not have an image.

Document repository URLs and languages for unbuilt components

Description

It is necessary to understand the skills and difficulty required to create patches for images and components.

List

Example

trivy:0.34.0
- URL: https://github.com/aquasecurity/trivy
- License: Apache-2.0 license
- Dockerfile URL: https://github.com/aquasecurity/trivy/blob/main/Dockerfile
- Dockerfile License: Apache-2.0 license
- Docker URL: docker.io/aquasec/trivy:0.34.0
- Supported Architectures: amd64, arm64, ppc64le, s390x
- Language: golang

Supported Bitnami chart list

Chart List

Chart
- Image

Generated from

go run main.go checkCharts --level=4

Todo

CI update this issue.
#48
- If there is an official chart, it's a low priority.

[question]: fixing CVEs in openldap image

I ran the openldap arm64 image through trivy and was seeing a few CVEs. These do not match with the bitnami/openldap:2.6 image.

% trivy image -s "HIGH,CRITICAL" bitnami/openldap:2.6 | grep -i total -B2

2022-10-03T14:42:47.577+0530	INFO	Vulnerability scanning is enabled
2022-10-03T14:42:47.577+0530	INFO	Secret scanning is enabled
2022-10-03T14:42:47.577+0530	INFO	If your scanning is slow, please try '--security-checks vuln' to disable secret scanning
2022-10-03T14:42:47.577+0530	INFO	Please see also https://aquasecurity.github.io/trivy/v0.32/docs/secret/scanning/#recommendation for faster secret detection
2022-10-03T14:42:55.773+0530	INFO	Detected OS: debian
2022-10-03T14:42:55.773+0530	INFO	Detecting Debian vulnerabilities...
2022-10-03T14:42:55.787+0530	INFO	Number of language-specific files: 1
2022-10-03T14:42:55.787+0530	INFO	Detecting gobinary vulnerabilities...
bitnami/openldap:2.6 (debian 11.5)
==================================
Total: 10 (HIGH: 9, CRITICAL: 1)
--
opt/bitnami/common/bin/gosu (gobinary)
======================================
Total: 1 (HIGH: 1, CRITICAL: 0)

% trivy image -s "HIGH,CRITICAL" ghcr.io/zcube/bitnami-compat/openldap:2.6.3 | grep -i total -B2

2022-10-03T14:43:37.962+0530	INFO	Vulnerability scanning is enabled
2022-10-03T14:43:37.962+0530	INFO	Secret scanning is enabled
2022-10-03T14:43:37.962+0530	INFO	If your scanning is slow, please try '--security-checks vuln' to disable secret scanning
2022-10-03T14:43:37.962+0530	INFO	Please see also https://aquasecurity.github.io/trivy/v0.32/docs/secret/scanning/#recommendation for faster secret detection
2022-10-03T14:43:38.004+0530	INFO	Detected OS: debian
2022-10-03T14:43:38.004+0530	INFO	Detecting Debian vulnerabilities...
2022-10-03T14:43:38.023+0530	INFO	Number of language-specific files: 1
2022-10-03T14:43:38.023+0530	INFO	Detecting gobinary vulnerabilities...
ghcr.io/zcube/bitnami-compat/openldap:2.6.3 (debian 11.5)
=========================================================
Total: 84 (HIGH: 83, CRITICAL: 1)
--
opt/bitnami/common/bin/gosu (gobinary)
======================================
Total: 1 (HIGH: 1, CRITICAL: 0)

i.e. around 70 additional ones.
on a more verbose output it looks like the majority of the CVEs are for mariadb-common and libmariadb3
there was no explicit install in the Dockerfile for mariadb, so was wondering how could we upgrade this and fix the CVEs?

thanks

Keycloak is different between bitnami and bitnami-compat

I've been struggling a lot getting Keycloak configured to work correctly behind an nginx-ingress, and in the end found out that the environment variables the chart from bitnami set were not matching what the container needed.

I openend a ticket here bitnami/charts#11358 but it seems that the Keycloak installed differs between this patched container and the original bitnami one.

Kafka images are missing Java after rebase to latest commit

Fails to start because there is no Java.

Luckily tag 3 is not reused, so, it is easy to illustrate it.

Old image podman run

podman run -it --rm --entrypoint /bin/sh ghcr.io/zcube/bitnami-compat/kafka:3 -c "java -version"
openjdk version "11.0.13" 2021-10-19
OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8)
OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode)

New image podman run

podman run -it --rm --entrypoint /bin/sh ghcr.io/zcube/bitnami-compat/kafka:3.2 -c "java -version"
/bin/sh: 1: java: not found

Bump was requested in scope of #17

Permission issue for Postgresql 14 using a strict security context

I think the arm build is setting the permissions different here as well

Build squash image for size reduction.

JIT-related segmentation fault issue when building rabbitmq on arm64

Hello I am trying to build the rabbitmq apple silicone image and I get a segmentation fault
I am running this on a Macbook Pro M1.
macOS Monterey 12.6.2

36 1043.0             -e 's;%INETS_VSN%;7.5.3;' \
#36 1043.0           /usr/local/src/otp-24.3.4/erts/start_scripts/start_all_example.rel.src > /usr/local/src/otp-24.3.4/erts/start_scripts/start_all_example.rel
#36 1043.0 sed -e 's;%SYS_VSN%;24;' \
#36 1043.0             -e 's;%ERTS_VSN%;12.3.2;' \
#36 1043.0             -e 's;%KERNEL_VSN%;8.3.2;' \
#36 1043.0             -e 's;%STDLIB_VSN%;3.17.2;' \
#36 1043.0           /usr/local/src/otp-24.3.4/erts/start_scripts/no_dot_erlang.rel.src > /usr/local/src/otp-24.3.4/erts/start_scripts/no_dot_erlang.rel
#36 1043.1 /usr/bin/install -c -d /usr/local/src/otp-24.3.4/erts/start_scripts/tmp
#36 1043.1 ( cd /usr/local/src/otp-24.3.4/erts/start_scripts/tmp && \
#36 1043.1 erlc -W   -I/usr/local/src/otp-24.3.4/lib/kernel/ebin -I/usr/local/src/otp-24.3.4/lib/stdlib/ebin -I/usr/local/src/otp-24.3.4/lib/sasl/ebin +no_warn_sasl -o /usr/local/src/otp-24.3.4/erts/start_scripts /usr/local/src/otp-24.3.4/erts/start_scripts/start_clean.rel )
#36 1043.5 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#36 1043.5 Segmentation fault
#36 1043.5 make[2]: *** [Makefile:84: /usr/local/src/otp-24.3.4/erts/start_scripts/start_clean.script] Error 139
#36 1043.5 make[2]: Leaving directory '/usr/local/src/otp-24.3.4/erts/start_scripts'
#36 1043.5 make[1]: *** [Makefile:67: local_setup] Error 2
#36 1043.5 make[1]: Leaving directory '/usr/local/src/otp-24.3.4/erts'
#36 1043.5 make: *** [Makefile:1070: local_setup] Error 2
#36 ERROR: process "/bin/bash -o pipefail -c set -eux; \t\tsavedAptMark=\"$(apt-mark showmanual)\"; \tapt-get update; \tapt-get install --yes --no-install-recommends \t\tautoconf \t\tca-certificates \t\tdpkg-dev \t\tgcc \t\tg++ \t\tgnupg \t\tlibncurses5-dev \t\tmake \t\twget \t; \trm -rf /var/lib/apt/lists/*; \t\tOPENSSL_SOURCE_URL=\"https://www.openssl.org/source/openssl-$OPENSSL_VERSION.tar.gz\"; \tOPENSSL_PATH=\"/usr/local/src/openssl-$OPENSSL_VERSION\"; \tOPENSSL_CONFIG_DIR=/usr/local/etc/ssl; \t\twget --progress dot:giga --output-document \"$OPENSSL_PATH.tar.gz.asc\" \"$OPENSSL_SOURCE_URL.asc\"; \twget --progress dot:giga --output-document \"$OPENSSL_PATH.tar.gz\" \"$OPENSSL_SOURCE_URL\"; \texport GNUPGHOME=\"$(mktemp -d)\"; \tfor key in $OPENSSL_PGP_KEY_IDS; do \t\tgpg --batch --keyserver \"$PGP_KEYSERVER\" --recv-keys \"$key\"; \tdone; \tgpg --batch --verify \"$OPENSSL_PATH.tar.gz.asc\" \"$OPENSSL_PATH.tar.gz\"; \tgpgconf --kill all; \trm -rf \"$GNUPGHOME\"; \techo \"$OPENSSL_SOURCE_SHA256 *$OPENSSL_PATH.tar.gz\" | sha256sum --check --strict -; \tmkdir -p \"$OPENSSL_PATH\"; \ttar --extract --file \"$OPENSSL_PATH.tar.gz\" --directory \"$OPENSSL_PATH\" --strip-components 1; \t\tcd \"$OPENSSL_PATH\"; \tdebMultiarch=\"$(dpkg-architecture --query DEB_HOST_MULTIARCH)\"; \tMACHINE=\"$(dpkg-architecture --query DEB_BUILD_GNU_CPU)\" \tRELEASE=\"4.x.y-z\" \tSYSTEM='Linux' \tBUILD='???' \t./config \t\t--openssldir=\"$OPENSSL_CONFIG_DIR\" \t\t--libdir=\"lib/$debMultiarch\" \t\t-Wl,-rpath=/usr/local/lib \t; \tmake -j \"$(getconf _NPROCESSORS_ONLN)\"; \tmake install_sw install_ssldirs; \tcd ..; \trm -rf \"$OPENSSL_PATH\"*; \tldconfig; \trmdir \"$OPENSSL_CONFIG_DIR/certs\" \"$OPENSSL_CONFIG_DIR/private\"; \tln -sf /etc/ssl/certs /etc/ssl/private \"$OPENSSL_CONFIG_DIR\"; \topenssl version; \t\tOTP_SOURCE_URL=\"https://github.com/erlang/otp/releases/download/OTP-$OTP_VERSION/otp_src_$OTP_VERSION.tar.gz\"; \tOTP_SHA256_URL=\"https://github.com/erlang/otp/releases/download/OTP-$OTP_VERSION/SHA256.txt\"; \tOTP_PATH=\"/usr/local/src/otp-$OTP_VERSION\"; \t\tmkdir -p \"$OTP_PATH\"; \twget --progress dot:giga --output-document \"$OTP_PATH.tar.gz\" \"$OTP_SOURCE_URL\"; \twget --progress dot:giga --output-document \"SHA256.txt\" \"$OTP_SHA256_URL\"; \tcat SHA256.txt | grep \"otp_src\" | awk -v version=$OTP_VERSION '{print $1,\"otp-\" version \".tar.gz\"}' | sha256sum --check --strict -; \ttar --extract --file \"$OTP_PATH.tar.gz\" --directory \"$OTP_PATH\" --strip-components 1; \t\tcd \"$OTP_PATH\"; \texport ERL_TOP=\"$OTP_PATH\"; \t./otp_build autoconf; \tCFLAGS=\"$(dpkg-buildflags --get CFLAGS)\"; export CFLAGS; \texport CFLAGS=\"$CFLAGS -Wl,-rpath=/usr/local/lib\"; \thostArch=\"$(dpkg-architecture --query DEB_HOST_GNU_TYPE)\"; \tbuildArch=\"$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)\"; \tdpkgArch=\"$(dpkg --print-architecture)\"; dpkgArch=\"${dpkgArch##*-}\"; \tjitFlag=; \tcase \"$dpkgArch\" in \t\tamd64) jitFlag='--enable-jit' ;; \t\tarm64) jitFlag='--disable-jit' ;; \tesac; \t./configure \t\t--host=\"$hostArch\" \t\t--build=\"$buildArch\" \t\t--disable-dynamic-ssl-lib \t\t--disable-hipe \t\t--disable-sctp \t\t--disable-silent-rules \t\t--enable-clock-gettime \t\t--enable-hybrid-heap \t\t--enable-kernel-poll \t\t--enable-shared-zlib \t\t--enable-smp-support \t\t--enable-threads \t\t--with-microstate-accounting=extra \t\t--without-common_test \t\t--without-debugger \t\t--without-dialyzer \t\t--without-diameter \t\t--without-edoc \t\t--without-erl_docgen \t\t--without-et \t\t--without-eunit \t\t--without-ftp \t\t--without-hipe \t\t--without-jinterface \t\t--without-megaco \t\t--without-observer \t\t--without-odbc \t\t--without-reltool \t\t--without-ssh \t\t--without-tftp \t\t--without-wx \t\t$jitFlag \t; \tmake -j \"$(getconf _NPROCESSORS_ONLN)\" GEN_OPT_FLGS=\"-O2 -fno-strict-aliasing\"; \tmake install; \tcd ..; \trm -rf \t\t\"$OTP_PATH\"* \t\t/usr/local/lib/erlang/lib/*/examples \t\t/usr/local/lib/erlang/lib/*/src \t; \t\tapt-mark auto '.*' > /dev/null; \t[ -z \"$savedAptMark\" ] || apt-mark manual $savedAptMark; \tfind /usr/local -type f -executable -exec ldd '{}' ';' \t\t| awk '/=>/ { print $(NF-1) }' \t\t| sort -u \t\t| grep -v libcrypto \t\t| grep -v libssl \t\t| xargs -r dpkg-query --search \t\t| cut -d: -f1 \t\t| sort -u \t\t| xargs -r apt-mark manual \t; \tapt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; \t\topenssl version; \terl -noshell -eval 'io:format(\"~p~n~n~p~n~n\", [crypto:supports(), ssl:versions()]), init:stop().'" did not complete successfully: exit code: 2
------
 > importing cache manifest from 769032674102.dkr.ecr.us-east-1.amazonaws.com/mirror/docker.io/bitnami/rabbitmqrabbitmq:3.9:
------
------
 > [linux/amd64 stage-1  6/16] RUN set -eux; 		savedAptMark="$(apt-mark showmanual)"; 	apt-get update; 	apt-get install --yes --no-install-recommends 		autoconf 		ca-certificates 		dpkg-dev 		gcc 		g++ 		gnupg 		libncurses5-dev 		make 		wget 	; 	rm -rf /var/lib/apt/lists/*; 		OPENSSL_SOURCE_URL="https://www.openssl.org/source/openssl-$OPENSSL_VERSION.tar.gz"; 	OPENSSL_PATH="/usr/local/src/openssl-$OPENSSL_VERSION"; 	OPENSSL_CONFIG_DIR=/usr/local/etc/ssl; 		wget --progress dot:giga --output-document "$OPENSSL_PATH.tar.gz.asc" "$OPENSSL_SOURCE_URL.asc"; 	wget --progress dot:giga --output-document "$OPENSSL_PATH.tar.gz" "$OPENSSL_SOURCE_URL"; 	export GNUPGHOME="$(mktemp -d)"; 	for key in $OPENSSL_PGP_KEY_IDS; do 		gpg --batch --keyserver "$PGP_KEYSERVER" --recv-keys "$key"; 	done; 	gpg --batch --verify "$OPENSSL_PATH.tar.gz.asc" "$OPENSSL_PATH.tar.gz"; 	gpgconf --kill all; 	rm -rf "$GNUPGHOME"; 	echo "$OPENSSL_SOURCE_SHA256 *$OPENSSL_PATH.tar.gz" | sha256sum --check --strict -; 	mkdir -p "$OPENSSL_PATH"; 	tar --extract --file "$OPENSSL_PATH.tar.gz" --directory "$OPENSSL_PATH" --strip-components 1; 		cd "$OPENSSL_PATH"; 	debMultiarch="$(dpkg-architecture --query DEB_HOST_MULTIARCH)"; 	MACHINE="$(dpkg-architecture --query DEB_BUILD_GNU_CPU)" 	RELEASE="4.x.y-z" 	SYSTEM='Linux' 	BUILD='???' 	./config 		--openssldir="$OPENSSL_CONFIG_DIR" 		--libdir="lib/$debMultiarch" 		-Wl,-rpath=/usr/local/lib 	; 	make -j "$(getconf _NPROCESSORS_ONLN)"; 	make install_sw install_ssldirs; 	cd ..; 	rm -rf "$OPENSSL_PATH"*; 	ldconfig; 	rmdir "$OPENSSL_CONFIG_DIR/certs" "$OPENSSL_CONFIG_DIR/private"; 	ln -sf /etc/ssl/certs /etc/ssl/private "$OPENSSL_CONFIG_DIR"; 	openssl version; 		OTP_SOURCE_URL="https://github.com/erlang/otp/releases/download/OTP-$OTP_VERSION/otp_src_$OTP_VERSION.tar.gz"; 	OTP_SHA256_URL="https://github.com/erlang/otp/releases/download/OTP-$OTP_VERSION/SHA256.txt"; 	OTP_PATH="/usr/local/src/otp-$OTP_VERSION"; 		mkdir -p "$OTP_PATH"; 	wget --progress dot:giga --output-document "$OTP_PATH.tar.gz" "$OTP_SOURCE_URL"; 	wget --progress dot:giga --output-document "SHA256.txt" "$OTP_SHA256_URL"; 	cat SHA256.txt | grep "otp_src" | awk -v version=$OTP_VERSION '{print $1,"otp-" version ".tar.gz"}' | sha256sum --check --strict -; 	tar --extract --file "$OTP_PATH.tar.gz" --directory "$OTP_PATH" --strip-components 1; 		cd "$OTP_PATH"; 	export ERL_TOP="$OTP_PATH"; 	./otp_build autoconf; 	CFLAGS="$(dpkg-buildflags --get CFLAGS)"; export CFLAGS; 	export CFLAGS="$CFLAGS -Wl,-rpath=/usr/local/lib"; 	hostArch="$(dpkg-architecture --query DEB_HOST_GNU_TYPE)"; 	buildArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; 	dpkgArch="$(dpkg --print-architecture)"; dpkgArch="${dpkgArch##*-}"; 	jitFlag=; 	case "$dpkgArch" in 		amd64) jitFlag='--enable-jit' ;; 		arm64) jitFlag='--disable-jit' ;; 	esac; 	./configure 		--host="$hostArch" 		--build="$buildArch" 		--disable-dynamic-ssl-lib 		--disable-hipe 		--disable-sctp 		--disable-silent-rules 		--enable-clock-gettime 		--enable-hybrid-heap 		--enable-kernel-poll 		--enable-shared-zlib 		--enable-smp-support 		--enable-threads 		--with-microstate-accounting=extra 		--without-common_test 		--without-debugger 		--without-dialyzer 		--without-diameter 		--without-edoc 		--without-erl_docgen 		--without-et 		--without-eunit 		--without-ftp 		--without-hipe 		--without-jinterface 		--without-megaco 	--without-observer 		--without-odbc 		--without-reltool 		--without-ssh 		--without-tftp 		--without-wx 		$jitFlag 	; 	make -j "$(getconf _NPROCESSORS_ONLN)" GEN_OPT_FLGS="-O2 -fno-strict-aliasing"; 	make install; 	cd ..; 	rm -rf 		"$OTP_PATH"* 		/usr/local/lib/erlang/lib/*/examples 		/usr/local/lib/erlang/lib/*/src 	; 		apt-mark auto '.*' > /dev/null; 	[ -z "$savedAptMark" ] || apt-mark manual $savedAptMark; 	find /usr/local -type f -executable -exec ldd '{}' ';' 		| awk '/=>/ { print $(NF-1) }' 		| sort -u 		| grep -v libcrypto 		| grep -v libssl 		| xargs -r dpkg-query --search 		| cut -d: -f1 		| sort -u | xargs -r apt-mark manual 	; 	apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; 		openssl version; 	erl -noshell -eval 'io:format("~p~n~n~p~n~n", [crypto:supports(), ssl:versions()]), init:stop().':
#36 1043.1 /usr/bin/install -c -d /usr/local/src/otp-24.3.4/erts/start_scripts/tmp
#36 1043.1 ( cd /usr/local/src/otp-24.3.4/erts/start_scripts/tmp && \
#36 1043.1 erlc -W   -I/usr/local/src/otp-24.3.4/lib/kernel/ebin -I/usr/local/src/otp-24.3.4/lib/stdlib/ebin -I/usr/local/src/otp-24.3.4/lib/sasl/ebin +no_warn_sasl -o /usr/local/src/otp-24.3.4/erts/start_scripts /usr/local/src/otp-24.3.4/erts/start_scripts/start_clean.rel )
#36 1043.5 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#36 1043.5 Segmentation fault
#36 1043.5 make[2]: *** [Makefile:84: /usr/local/src/otp-24.3.4/erts/start_scripts/start_clean.script] Error 139
#36 1043.5 make[2]: Leaving directory '/usr/local/src/otp-24.3.4/erts/start_scripts'
#36 1043.5 make[1]: *** [Makefile:67: local_setup] Error 2
#36 1043.5 make[1]: Leaving directory '/usr/local/src/otp-24.3.4/erts'
#36 1043.5 make: *** [Makefile:1070: local_setup] Error 2
------
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Dockerfile.arm64:129
--------------------
 128 |     # libncurses5-dev: Required for Erlang/OTP new shell & observer_cli - https://github.com/zhongwencool/observer_cli
 129 | >>> RUN set -eux; \
 130 | >>> 	\

 278 | >>> 	\
 279 | >>> # Check that OpenSSL still works after purging build dependencies
 280 | >>> 	openssl version; \
 281 | >>> # Check that Erlang/OTP crypto & ssl were compiled against OpenSSL correctly
 282 | >>> 	erl -noshell -eval 'io:format("~p~n~n~p~n~n", [crypto:supports(), ssl:versions()]), init:stop().'
 283 |     
--------------------
ERROR: failed to solve: process "/bin/bash -o pipefail -c set -eux; \t\tsavedAptMark=\"$(apt-mark showmanual)\"; \tapt-get update; \tapt-get install --yes --no-install-recommends \t\tautoconf \t\tca-certificates \t\tdpkg-dev \t\tgcc \t\tg++ \t\tgnupg \t\tlibncurses5-dev \t\tmake \t\twget \t; \trm -rf /var/lib/apt/lists/*; \t\tOPENSSL_SOURCE_URL=\"https://www.openssl.org/source/openssl-$OPENSSL_VERSION.tar.gz\"; \tOPENSSL_PATH=\"/usr/local/src/openssl-$OPENSSL_VERSION\"; \tOPENSSL_CONFIG_DIR=/usr/local/etc/ssl; \t\twget --progress dot:giga --output-document \"$OPENSSL_PATH.tar.gz.asc\" \"$OPENSSL_SOURCE_URL.asc\"; \twget --progress dot:giga --output-document \"$OPENSSL_PATH.tar.gz\" \"$OPENSSL_SOURCE_URL\"; \texport GNUPGHOME=\"$(mktemp -d)\"; \tfor key in $OPENSSL_PGP_KEY_IDS; do \t\tgpg --batch --keyserver \"$PGP_KEYSERVER\" --recv-keys \"$key\"; \tdone; \tgpg --batch --verify \"$OPENSSL_PATH.tar.gz.asc\" \"$OPENSSL_PATH.tar.gz\"; \tgpgconf --kill all; \trm -rf \"$GNUPGHOME\"; \techo \"$OPENSSL_SOURCE_SHA256 *$OPENSSL_PATH.tar.gz\" | sha256sum --check --strict -; \tmkdir -p \"$OPENSSL_PATH\"; \ttar --extract --file \"$OPENSSL_PATH.tar.gz\" --directory \"$OPENSSL_PATH\" --strip-components 1; \t\tcd \"$OPENSSL_PATH\"; \tdebMultiarch=\"$(dpkg-architecture --query DEB_HOST_MULTIARCH)\"; \tMACHINE=\"$(dpkg-architecture --query DEB_BUILD_GNU_CPU)\" \tRELEASE=\"4.x.y-z\" \tSYSTEM='Linux' \tBUILD='???' \t./config \t\t--openssldir=\"$OPENSSL_CONFIG_DIR\" \t\t--libdir=\"lib/$debMultiarch\" \t\t-Wl,-rpath=/usr/local/lib \t; \tmake -j \"$(getconf _NPROCESSORS_ONLN)\"; \tmake install_sw install_ssldirs; \tcd ..; \trm -rf \"$OPENSSL_PATH\"*; \tldconfig; \trmdir \"$OPENSSL_CONFIG_DIR/certs\" \"$OPENSSL_CONFIG_DIR/private\"; \tln -sf /etc/ssl/certs /etc/ssl/private \"$OPENSSL_CONFIG_DIR\"; \topenssl version; \t\tOTP_SOURCE_URL=\"https://github.com/erlang/otp/releases/download/OTP-$OTP_VERSION/otp_src_$OTP_VERSION.tar.gz\"; \tOTP_SHA256_URL=\"https://github.com/erlang/otp/releases/download/OTP-$OTP_VERSION/SHA256.txt\"; \tOTP_PATH=\"/usr/local/src/otp-$OTP_VERSION\"; \t\tmkdir -p \"$OTP_PATH\"; \twget --progress dot:giga --output-document \"$OTP_PATH.tar.gz\" \"$OTP_SOURCE_URL\"; \twget --progress dot:giga --output-document \"SHA256.txt\" \"$OTP_SHA256_URL\"; \tcat SHA256.txt | grep \"otp_src\" | awk -v version=$OTP_VERSION '{print $1,\"otp-\" version \".tar.gz\"}' | sha256sum --check --strict -; \ttar --extract --file \"$OTP_PATH.tar.gz\" --directory \"$OTP_PATH\" --strip-components 1; \t\tcd \"$OTP_PATH\"; \texport ERL_TOP=\"$OTP_PATH\"; \t./otp_build autoconf; \tCFLAGS=\"$(dpkg-buildflags --get CFLAGS)\"; export CFLAGS; \texport CFLAGS=\"$CFLAGS -Wl,-rpath=/usr/local/lib\"; \thostArch=\"$(dpkg-architecture --query DEB_HOST_GNU_TYPE)\"; \tbuildArch=\"$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)\"; \tdpkgArch=\"$(dpkg --print-architecture)\"; dpkgArch=\"${dpkgArch##*-}\"; \tjitFlag=; \tcase \"$dpkgArch\" in \t\tamd64) jitFlag='--enable-jit' ;; \t\tarm64) jitFlag='--disable-jit' ;; \tesac; \t./configure \t\t--host=\"$hostArch\" \t\t--build=\"$buildArch\" \t\t--disable-dynamic-ssl-lib \t\t--disable-hipe \t\t--disable-sctp \t\t--disable-silent-rules \t\t--enable-clock-gettime \t\t--enable-hybrid-heap \t\t--enable-kernel-poll \t\t--enable-shared-zlib \t\t--enable-smp-support \t\t--enable-threads \t\t--with-microstate-accounting=extra \t\t--without-common_test \t\t--without-debugger \t\t--without-dialyzer \t\t--without-diameter \t\t--without-edoc \t\t--without-erl_docgen \t\t--without-et \t\t--without-eunit \t\t--without-ftp \t\t--without-hipe \t\t--without-jinterface \t\t--without-megaco \t\t--without-observer \t\t--without-odbc \t\t--without-reltool \t\t--without-ssh \t\t--without-tftp \t\t--without-wx \t\t$jitFlag \t; \tmake -j \"$(getconf _NPROCESSORS_ONLN)\" GEN_OPT_FLGS=\"-O2 -fno-strict-aliasing\"; \tmake install; \tcd ..; \trm -rf \t\t\"$OTP_PATH\"* \t\t/usr/local/lib/erlang/lib/*/examples \t\t/usr/local/lib/erlang/lib/*/src \t; \t\tapt-mark auto '.*' > /dev/null; \t[ -z \"$savedAptMark\" ] || apt-mark manual $savedAptMark; \tfind /usr/local -type f -executable -exec ldd '{}' ';' \t\t| awk '/=>/ { print $(NF-1) }' \t\t| sort -u \t\t| grep -v libcrypto \t\t| grep -v libssl \t\t| xargs -r dpkg-query --search \t\t| cut -d: -f1 \t\t| sort -u \t\t| xargs -r apt-mark manual \t; \tapt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; \t\topenssl version; \terl -noshell -eval 'io:format(\"~p~n~n~p~n~n\", [crypto:supports(), ssl:versions()]), init:stop().'" did not complete successfully: exit code: 2
2023/01/09 12:40:39 exit status 1
panic: exit status 1

goroutine 1 [running]:
log.Panic({0x140000ddc10?, 0x6?, 0x140001bea80?})
	/Users/nmetchev/.asdf/installs/golang/1.19.3/go/src/log/log.go:388 +0x64
github.com/zcube/bitnami-compat/cmd.glob..func1(0x10516d2e0?, {0x104aacd6d?, 0x4?, 0x4?})
	/Users/nmetchev/dev/bitnami-compat/cmd/build.go:165 +0xbe4
github.com/spf13/cobra.(*Command).execute(0x10516d2e0, {0x140001c6480, 0x4, 0x4})
	/Users/nmetchev/dev/gopath/pkg/mod/github.com/spf13/[email protected]/command.go:876 +0x4b8
github.com/spf13/cobra.(*Command).ExecuteC(0x10516d7e0)
	/Users/nmetchev/dev/gopath/pkg/mod/github.com/spf13/[email protected]/command.go:990 +0x354
github.com/spf13/cobra.(*Command).Execute(...)
	/Users/nmetchev/dev/gopath/pkg/mod/github.com/spf13/[email protected]/command.go:918
github.com/zcube/bitnami-compat/cmd.Execute()
	/Users/nmetchev/dev/bitnami-compat/cmd/root.go:47 +0x28
main.main()
	/Users/nmetchev/dev/bitnami-compat/main.go:27 +0x1c
exit status 2

Postgres config incorrect

Hi, I built postgresql 14.6.0 from your repo, but it seems to be creating an incorrect image. I get the following error when i use it in conjunction with the bitnami helm chart:
This is how I install it

 helm install -n testpostgres2 --set image.debug=true --set image.tag=14.6.0-debian-11-r50 --set image.registry=<custom_registry> --create-namespace  postgresqltest bitnami/postgresql

This is the error that occurs on startup:

postgresql
2023-01-11 08:40:41.310 GMT [1] LOG: unrecognized configuration parameter "wal_keep_segments" in file "/opt/bitnami/postgresql/conf/postgresql.conf" line 800
postgresql
2023-01-11 08:40:41.311 GMT [1] FATAL: configuration file "/opt/bitnami/postgresql/conf/postgresql.conf" contains errors

If I use the official bitnami docker images this doesn't happen.

Wordpress support

Hi @ZCube - Thanks for your work creating this compatibility layer!

@shawngerrard and I are currently using this for a deployment of Mariadb which is working great, now we need to extend the repository to add wordpress. I've created a fork and begun stepping through the instructions for adding a new image, however I'm getting a bit stuck at step 3.

Is there any more context available about how these scripts fit together and how they relate to introducing something like wordpress?

If you could provide some gentle guidance I'm happy to complete the pull request to get this added, thanks!

discourse: Some required software is not installed.

Thank you for these arm64 versions, this really makes development on apple m1 a lot better.

It looks like the Phusion Passenger(R) agent binary is not available for arm64 it tries to compile it itself, but fails because some requirements

* To install Curl development headers with SSL support:
Please run apt-get install libcurl4-openssl-dev or libcurl4-gnutls-dev, whichever you prefer.

are not present in the container.

Full docker compose log here:

webapp-server-discourse_1              | discourse 14:15:27.08 INFO  ==> Creating database user cncplatformdiscourse
webapp-server-discourse_1              | discourse 14:15:27.10 INFO  ==> Creating database cncplatformdiscourse
webapp-server-discourse_1              | discourse 14:15:27.18 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
webapp-server-discourse_1              | discourse 14:15:27.19 INFO  ==> Creating Discourse configuration file
webapp-server-discourse_1              | discourse 14:15:27.26 INFO  ==> Enabling SMTP
webapp-server-discourse_1              | discourse 14:15:27.33 INFO  ==> Restoring persisted Discourse installation
webapp-server-discourse_1              | discourse 14:15:27.38 INFO  ==> Trying to connect to the database server
webapp-server-discourse_1              | discourse 14:15:27.40 INFO  ==> Running database migrations
webapp-server-discourse_1              | discourse 14:15:30.37 INFO  ==> Populating CSS cache in database
webapp-server-discourse_1              | discourse 14:15:33.39 INFO  ==> ** Discourse setup finished! **
webapp-server-discourse_1              | 
webapp-server-discourse_1              | discourse 14:15:33.41 INFO  ==> ** Starting Discourse **
webapp-server-discourse_1              |  --> Downloading a Phusion Passenger(R) agent binary for your platform
webapp-server-discourse_1              |      Could not download https://github.com/phusion/passenger/releases/download/release-6.0.15/agent-aarch64-linux.tar.gz: 2022-11-04 14:15:35 ERROR 404: Not Found.
webapp-server-discourse_1              |      Trying next mirror...
webapp-server-discourse_1              |      Could not download https://oss-binaries.phusionpassenger.com/binaries/passenger/by_release/6.0.15/agent-aarch64-linux.tar.gz: 2022-11-04 14:15:35 ERROR 404: Not Found.
webapp-server-discourse_1              |      Trying next mirror...
webapp-server-discourse_1              |      Could not download https://s3.amazonaws.com/phusion-passenger/binaries/passenger/by_release/6.0.15/agent-aarch64-linux.tar.gz: 2022-11-04 14:15:37 ERROR 403: Forbidden.
webapp-server-discourse_1              |      ------------------------------------------
webapp-server-discourse_1              |      Sorry, no precompiled agent binary is available for your platform.
webapp-server-discourse_1              | 
webapp-server-discourse_1              | ---------------------------------------
webapp-server-discourse_1              | 
webapp-server-discourse_1              | The Phusion Passenger(R) agent binary could not be downloaded. Compiling it from source instead.
webapp-server-discourse_1              | 
webapp-server-discourse_1              | Checking for required software...
webapp-server-discourse_1              | 
webapp-server-discourse_1              |  * Checking for C compiler...
webapp-server-discourse_1              |       Found: yes
webapp-server-discourse_1              |       Location: /usr/bin/cc
webapp-server-discourse_1              |  * Checking for C++ compiler...
webapp-server-discourse_1              |       Found: yes
webapp-server-discourse_1              |       Location: /usr/bin/c++
webapp-server-discourse_1              |  * Checking for Rake (associated with /usr/local/bin/ruby)...
webapp-server-discourse_1              |       Found: yes
webapp-server-discourse_1              |       Location: /usr/local/bin/ruby /usr/local/bin/rake
webapp-server-discourse_1              |  * Checking for Curl development headers with SSL support...
webapp-server-discourse_1              |       Found: no
webapp-server-discourse_1              |       Error: Cannot find the `curl-config` command.
webapp-server-discourse_1              |  * Checking for OpenSSL development headers...
webapp-server-discourse_1              |       Found: yes
webapp-server-discourse_1              |       Location: /usr/include/openssl/ssl.h
webapp-server-discourse_1              |  * Checking for Zlib development headers...
webapp-server-discourse_1              |       Found: yes
webapp-server-discourse_1              |       Location: /usr/include/zlib.h
webapp-server-discourse_1              | 
webapp-server-discourse_1              | Some required software is not installed.
webapp-server-discourse_1              | But don't worry, this installer will tell you how to install them.
webapp-server-discourse_1              | Press Enter to continue, or Ctrl-C to abort.
webapp-server-discourse_1              | --------------------------------------------
webapp-server-discourse_1              | 
webapp-server-discourse_1              | Installation instructions for required software
webapp-server-discourse_1              | 
webapp-server-discourse_1              |  * To install Curl development headers with SSL support:
webapp-server-discourse_1              |    Please run apt-get install libcurl4-openssl-dev or libcurl4-gnutls-dev, whichever you prefer.
webapp-server-discourse_1              | 
webapp-server-discourse_1              | If the aforementioned instructions didn't solve your problem, then please take
webapp-server-discourse_1              | a look at our documentation for troubleshooting tips:
webapp-server-discourse_1              | 
webapp-server-discourse_1              |   https://www.phusionpassenger.com/library/install/standalone/
webapp-server-discourse_1              |   https://www.phusionpassenger.com/library/admin/standalone/troubleshooting/

Request for bitnami/keycloak-config-cli

I use it in the helm chart to preconfigure the realm, but it just does nothing when running the and version.

It does not look like there is anything difficult installed (java and a jar file) but I don't really know how to get started on a PR.

  keycloakConfigCli:
    enabled: true
    backoffLimit: 3
    # https://github.com/bitnami/charts/issues/10796
    command:
      - java
      - -jar
      - /opt/bitnami/keycloak-config-cli/keycloak-config-cli-18.0.1.jar
    extraVolumes:
      - name: secret-volume
        secret:
          secretName: secondary-keycloak-config
    extraVolumeMounts:
      - name: secret-volume
        mountPath: "/custom-config"
        readOnly: true
    extraEnvVars:
      - name: IMPORT_FILES_LOCATIONS
        value: /custom-config/*

Bump kafka submodule to latest commit to support KRaft

Bitnami with the help of community recently added changes to support KRaft (kafka w/o zookeeper). Would be nice to have this in bitnami-compat with arm64 builds.

Thanos support

Please considering adding support for thanos.

Supported Bitnami image list

Image List

Image
- Component

Generated from

go run main.go list

Todo

CI update this issue.
#49

Classify if there is an official chart.

Either ~strikethrough~ if there is no first party helm chart, or a permalink to the latest tagged chart source code

Can't pull image for mongodb 5.0.6

Great work maintaining this repo.

when trying to pull mongodb 5.0.6 I keep getting manifest unknown.

image with tag 5.0.14 works perfectly.

thanks you.

Support for MySQL

Add the MySQL image (https://github.com/bitnami/bitnami-docker-mysql), this should be easy as we've done it before, I would do it but I forgot how to use your scripts. I would normally just clone it and modify it myself.

Wordpress version_module error

Hello @ZCube

I am trying to install the new wordpress version tag 6.0.3-debian-11-r35 but I am receiving this error from debug:

wordpress 06:09:54.99 INFO ==> Persisting WordPress installation
--
Mon, Oct 31 2022 12:09:57 am | wordpress 06:09:57.15 INFO ==> Executing /docker-entrypoint-init.d/..2022_10_31_06_09_13.295316030/00-configure-w3-total-cache.sh
Mon, Oct 31 2022 12:09:57 am | Plugin 'w3-total-cache' activated.
Mon, Oct 31 2022 12:09:57 am | Success: Activated 1 of 1 plugins.
Mon, Oct 31 2022 12:09:57 am | Success: Environment adjusted.
Mon, Oct 31 2022 12:09:58 am | Success: Option updated successfully.
Mon, Oct 31 2022 12:09:58 am | Success: Option updated successfully.
Mon, Oct 31 2022 12:09:59 am | Success: Everything flushed successfully.
Mon, Oct 31 2022 12:09:59 am | Success: Option updated successfully.
Mon, Oct 31 2022 12:09:59 am | Success: Option updated successfully.
Mon, Oct 31 2022 12:10:00 am | Success: Option updated successfully.
Mon, Oct 31 2022 12:10:00 am | Success: Option updated successfully.
Mon, Oct 31 2022 12:10:00 am | Success: Everything flushed successfully.
Mon, Oct 31 2022 12:10:00 am |  
Mon, Oct 31 2022 12:10:00 am | wordpress 06:10:00.88 INFO ==> ** WordPress setup finished! **
Mon, Oct 31 2022 12:10:00 am | wordpress 06:10:00.89 INFO ==> ** Starting Apache **
Mon, Oct 31 2022 12:10:00 am | httpd: Syntax error on line 120 of /opt/bitnami/apache/conf/httpd.conf: module version_module is built-in and can't be loaded

I can see this version_module was recently added

bitnami-compat/patches/apache/2/docker/Dockerfile.install

Lines 49 to 51 in a061961

    
           && sed -i 's,^\(LoadModule log_config_module modules/mod_log_config.so\),#\1,g' /opt/bitnami/apache/conf/httpd.conf \ 
        
           && sed -i 's,^\(LoadModule version_module modules/mod_version.so\),#\1,g' /opt/bitnami/apache/conf/httpd.conf \ 
        
           && sed -i 's,^\(LoadModule unixd_module modules/mod_unixd.so\),#\1,g' /opt/bitnami/apache/conf/httpd.conf \

Thanks for amazing job btw.

Move to `gitpod-arm/bitnami-compat`

Can we move this to gitpod-arm/bitnami-compat? It'll be easier to track since all the stuff will be in one place. I've already forked the repo.

Rabbitmq Operator Support

I am currently using the official rabbitmq guide to install it but it would be nicer to have support for the bitnami helm chart since is the one I am planning to use for the official production one and these images from this repository to test in my local macbook.

Also thanks for doing this! I was able to finally give some progress to this local testing thanks to your work.

Request: add external-dns

Unfortunately external-dns doesn't have official docker images, and it seems everyone using it is simply using it on amd64.

I appreciate that you're doing this because bitnami aren't and feel free to close with a "lol nope" kinda response, but it's one of the more annoying "just replace without bitnami" ones.

Cheers.

	&& sed -i 's,^\(LoadModule log_config_module modules/mod_log_config.so\),#\1,g' /opt/bitnami/apache/conf/httpd.conf \
	&& sed -i 's,^\(LoadModule version_module modules/mod_version.so\),#\1,g' /opt/bitnami/apache/conf/httpd.conf \
	&& sed -i 's,^\(LoadModule unixd_module modules/mod_unixd.so\),#\1,g' /opt/bitnami/apache/conf/httpd.conf \

zcube / bitnami-compat Goto Github PK

bitnami-compat's Introduction

Hi 👋, I'm ZCube

A hobbyist developer from Korea

bitnami-compat's People

Contributors

Stargazers

Watchers

Forkers

bitnami-compat's Issues

Test

Charts

Feature Description

Todo

Reference

Feature Description

Step 1. Create testing workflow

Reference:

Description

List

Example

Chart List

Todo

Image List

Todo

Recommend Projects

Recommend Topics

Recommend Org