Skip to content

Commit a2650ae

Browse files
authored
Merge pull request #1116 from SUSE/for-deploy-Basalt
🤖: Update build recipes for Basalt
2 parents efab12e + 0ff26b4 commit a2650ae

12 files changed

Lines changed: 54 additions & 18 deletions

File tree

busybox-image/README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,14 @@
1-
# SLE BCI-BusyBox: the smallest and GPLv3-free image
1+
# Basalt Project BCI Adaptable Linux Platform BusyBox: the smallest and GPLv3-free image
22
![Redistributable](https://img.shields.io/badge/Redistributable-Yes-green)
33
![Support Level](https://img.shields.io/badge/Support_Level-techpreview-blue)
44

5-
The SLE BCI-BusyBox image comes with the most basic tools provided by the BusyBox project.
5+
## Description
6+
This image comes with the most basic tools provided by the BusyBox project.
67
The image contains no GPLv3 licensed software. When using the image, keep in mind that
78
there are differences between the BusyBox tools and the GNU Coreutils.
89
This means that scripts written for a system that uses GNU Coreutils may require
910
modification to work with BusyBox. If you need a SLES compatible image with the GNU Coreutils,
10-
consider using the SLE BCI-Micro image instead.
11+
consider using the corresponding Micro image instead.
1112

1213
## Licensing
1314
`SPDX-License-Identifier: MIT`

busybox-image/busybox-image.changes

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
-------------------------------------------------------------------
2+
Wed May 8 16:26:23 UTC 2024 - Dirk Mueller <dmueller@suse.com>
3+
4+
- README fixes - better titles and follow recommended document structure
5+
16
-------------------------------------------------------------------
27
Tue May 7 19:13:26 UTC 2024 - Dirk Mueller <dmueller@suse.com>
38

mariadb-image/README.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
# MariaDB Server Container Image
22

3+
## Description
34
MariaDB is an open-source, multi-threaded, relational database management system. It's a backward-compatible branch of the MySQL Community Server that provides a drop-in replacement for MySQL.
45

5-
## Using the image
66

7+
## Usage
78
By default, the image launches MariaDB with the same configuration that comes with SUSE Linux Enterprise Server, with two exceptions: logging is sent to stdout, and binding to `localhost` is disabled.
89

910
The only environment variable required to start the container is the MariaDB root password.
@@ -18,7 +19,7 @@ or:
1819
$ podman run -it --rm -p 3306:3306 -e MARIADB_ALLOW_EMPTY_ROOT_PASSWORD=1 registry.suse.com/suse/mariadb:%%mariadb_version%%
1920
```
2021

21-
## Volumes
22+
### Volumes
2223

2324
The database is stored in the directory `/var/lib/mysql`.
2425

@@ -35,15 +36,15 @@ $ podman run -it --rm -v /my/own/datadir:/var/lib/mysql:Z -p 3306:3306 -e MARIAD
3536

3637
The `-v /my/own/datadir:/var/lib/mysql:Z` part of the command mounts the `/my/own/datadir` directory from the underlying host system as `/var/lib/mysql` inside the container, where MariaDB will by default write its data files.
3738

38-
## Environment Variables
39+
### Environment variables
3940

4041
One of `MARIADB_RANDOM_ROOT_PASSWORD`, `MARIADB_ROOT_PASSWORD_HASH`, `MARIADB_ROOT_PASSWORD` or `MARIADB_ALLOW_EMPTY_ROOT_PASSWORD` (or equivalents, including `*_FILE`), is required.
4142

4243
All other environment variables are optional.
4344

4445
All environment variables are documented in the MariaDB's Knowledge Base [MariaDB Server Docker Official Image Environment Variables](https://mariadb.com/kb/en/mariadb-server-docker-official-image-environment-variables/).
4546

46-
## Health, liveness and readiness
47+
### Health, liveness and readiness
4748

4849
There are no explicit health checks added to the container image. However, you can use the `healthcheck.sh` script to choose from a limited selection of tests to check for what you consider health, liveness, and readiness.
4950

@@ -57,7 +58,7 @@ If you start a MariaDB container instance with a data directory that already con
5758

5859
The only exception is the `MARIADB_AUTO_UPGRADE` environment variable. If it's set, it may run `mysql_upgrade` or `mariadb-upgrade`, potentially causing changes to the system tables.
5960

60-
## Backup and restore
61+
### Backup and restore
6162

6263
Information on how to perform backup and restore can be found on the MariaDB Knowledge Base [Container Backup and Restoration](https://mariadb.com/kb/en/container-backup-and-restoration/).
6364

mariadb-image/mariadb-image.changes

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
-------------------------------------------------------------------
2+
Wed May 8 16:26:23 UTC 2024 - Dirk Mueller <dmueller@suse.com>
3+
4+
- README fixes - better titles and follow recommended document structure
5+
16
-------------------------------------------------------------------
27
Tue May 7 19:13:26 UTC 2024 - Dirk Mueller <dmueller@suse.com>
38

micro-image/README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,13 @@
1-
# SLE BCI-Micro: Suitable for deploying static binaries
1+
# Basalt Project BCI Adaptable Linux Platform Micro: Suitable for deploying static binaries
22
![Redistributable](https://img.shields.io/badge/Redistributable-Yes-green)
33
![Support Level](https://img.shields.io/badge/Support_Level-techpreview-blue)
4-
This image is similar to SLE BCI-Minimal but without the RPM package manager.
4+
5+
## Description
6+
This image is similar to Minimal but without the RPM package manager.
57
The primary use case for the image is deploying static binaries produced
68
externally or during multi-stage builds. As there is no straightforward
79
way to install additional dependencies inside the container image,
8-
we recommend deploying a project using the SLE BCI-Minimal image only
10+
we recommend deploying a project using the Minimal image only
911
when the final build artifact bundles all dependencies and has no
1012
external runtime requirements (like Python or Ruby).
1113

micro-image/micro-image.changes

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
-------------------------------------------------------------------
2+
Wed May 8 16:26:23 UTC 2024 - Dirk Mueller <dmueller@suse.com>
3+
4+
- README fixes - better titles and follow recommended document structure
5+
16
-------------------------------------------------------------------
27
Tue May 7 19:13:26 UTC 2024 - Dirk Mueller <dmueller@suse.com>
38

minimal-image/README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,11 @@
1-
# SLE BCI-Minimal: Base Container image without Zypper
1+
# Basalt Project BCI Adaptable Linux Platform Minimal: Base Container image without Zypper
22
![Redistributable](https://img.shields.io/badge/Redistributable-Yes-green)
33
![Support Level](https://img.shields.io/badge/Support_Level-techpreview-blue)
4-
SLE BCI-Minimal comes without Zypper, but it does have the RPM package manager installed.
4+
5+
## Description
6+
This image comes without Zypper, but it does have the RPM package manager installed.
57
While RPM can install and remove packages, it lacks support for repositories and automated dependency resolution.
6-
The SLE BCI-Minimal image is therefore intended for creating deployment containers, and then installing the desired
8+
It is therefore intended for creating deployment containers, and then installing the desired
79
RPM packages inside the containers.
810

911
While you can install the required dependencies, you need to download and resolve them manually.

minimal-image/minimal-image.changes

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
-------------------------------------------------------------------
2+
Wed May 8 16:26:23 UTC 2024 - Dirk Mueller <dmueller@suse.com>
3+
4+
- README fixes - better titles and follow recommended document structure
5+
16
-------------------------------------------------------------------
27
Tue May 7 19:13:26 UTC 2024 - Dirk Mueller <dmueller@suse.com>
38

tomcat-10-image/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22

33
![Support Level](https://img.shields.io/badge/Support_Level-techpreview-blue)
44

5+
## Description
56
Apache Tomcat (Tomcat for short) is a free and open-source implementation of the
67
Jakarta Servlet, Jakarta Expression Language, and WebSocket technologies. It
78
provides a pure Java HTTP web server environment that can run Java code. It is a
89
Java web application server and not a complete JEE application server.
910

1011

11-
## How to use the image
12-
12+
## Usage
1313
By default, the image launches Tomcat with the same configuration as the one
1414
that comes with SUSE Linux Enterprise Server. The difference is that logging is
1515
sent to stdout, meaning that the `podman logs tomcat` command displays Tomcat

tomcat-10-image/tomcat-10-image.changes

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
-------------------------------------------------------------------
2+
Wed May 8 16:26:23 UTC 2024 - Dirk Mueller <dmueller@suse.com>
3+
4+
- README fixes - better titles and follow recommended document structure
5+
16
-------------------------------------------------------------------
27
Tue May 7 19:13:26 UTC 2024 - Dirk Mueller <dmueller@suse.com>
38

0 commit comments

Comments
 (0)