|
4 | 4 |
|
5 | 5 | ## Description |
6 | 6 |
|
7 | | -SUSE Linux Enterprise Base Container Images (SLE BCI) provide truly open, |
8 | | -flexible, and secure container images and application development tools. The |
9 | | -images consist of container environments based on SUSE Linux Enterprise and |
10 | | -designed to be a secure base for any containerized workload. |
11 | | - |
12 | | -SLE BCI is freely available, re-distributable, and supported across many |
13 | | -different environments. These templates and tools address modern, containerized |
14 | | -application development and CI/CD application containerization. They can be |
15 | | -used immediately by developers and integrators without the “lock-in” imposed by |
16 | | -other offerings. |
17 | | - |
18 | | -SLE BCI inherits industry-leading security and compliance from SUSE Linux |
19 | | -within your container build process. The container images are designed to be a |
20 | | -secure base for any application workload. SUSE ensures that compliance |
21 | | -standards are applied consistently and continuously improves security-related |
22 | | -capabilities. |
23 | | - |
24 | | -SLE BCI is lightweight and easy to adopt, with the ability to run with any |
25 | | -Linux OS. Avoid lock-in imposed by other vendors and get exactly what you need, |
26 | | -fast. SLE BCI delivers a flexible developer experience that accounts for, |
27 | | -integrates with, and supports language-native tools and workflows. |
| 7 | +SUSE Linux Enterprise Base Container Images (SLE BCI) provide open, flexible, |
| 8 | +and secure container images. The images include container environments based on |
| 9 | +SUSE Linux Enterprise Server and are available at no cost, they can be freely |
| 10 | +re-distributed, and they are supported across different environments. |
| 11 | + |
| 12 | +The Base Container Image is an image used as a foundation for most SLE BCIs. The |
| 13 | +image is intended to be extended for further use, such as a development or a |
| 14 | +testing environment. |
| 15 | + |
| 16 | + |
| 17 | +## Usage |
| 18 | + |
| 19 | +The container image comes with the `zypper` package manager, the free `SLE_BCI` |
| 20 | +repository and the `container-suseconnect` utility. This allows you to access to |
| 21 | +the full SLE repositories with a valid SLE subscription. The image is designed |
| 22 | +to be extended by installing packages required for your specific scenario. |
| 23 | + |
| 24 | +To build a custom image using a `Containerfile` that includes the |
| 25 | +[`skopeo`](https://github.com/containers/skopeo) utility, create the following |
| 26 | +`Containerfile`: |
| 27 | +```Dockerfile |
| 28 | +FROM registry.suse.com/bci/bci-base:15.6 |
| 29 | +RUN set -euo pipefail; \ |
| 30 | + zypper -n ref; \ |
| 31 | + zypper -n in skopeo; \ |
| 32 | + zypper -n clean; \ |
| 33 | + rm -rf /var/log/{lastlog,tallylog,zypper.log,zypp/history,YaST2} |
| 34 | +``` |
| 35 | + |
| 36 | +Then build the container using `buildah`: |
| 37 | +```bash |
| 38 | +buildah bud -t bci-skopeo . |
| 39 | +``` |
| 40 | + |
| 41 | +The image can also be used interactively to create a container with skopeo |
| 42 | +installed in it: |
| 43 | +```ShellSession |
| 44 | +$ podman run -ti --rm registry.suse.com/bci/bci-base:15.6 |
| 45 | +# zypper -n in skopeo |
| 46 | +... |
| 47 | +# skopeo inspect -f "{{ .Name }}" docker://registry.suse.com/bci/bci-base:15.6 |
| 48 | +registry.suse.com/bci/bci-base |
| 49 | +``` |
| 50 | + |
| 51 | +### The SLE_BCI repository |
| 52 | + |
| 53 | +The container image comes with the free `SLE_BCI` repository. The repository |
| 54 | +contains a subset of all packages from SUSE Linux Enterprise. The packages are |
| 55 | +available free of charge, and they can be redistributed freely. However, they |
| 56 | +are provided without support. The repository also contains the latest version of |
| 57 | +packages only. |
| 58 | + |
| 59 | + |
| 60 | +### Getting access to the SLE repositories |
| 61 | + |
| 62 | +The `container-suseconnect` utility in the image can automatically add the full |
| 63 | +SUSE Linux Enterprise repositories into the running container if you have a |
| 64 | +valid SLE subscription. |
| 65 | + |
| 66 | +Find more information about container-suseconnect in the |
| 67 | +[`container-suseconnect`](https://documentation.suse.com/container/all/single-html/Container-guide/index.html#sec-container-suseconnect) |
| 68 | +section in the container guide or in the tutorial ["How to use |
| 69 | +container-suseconnect"](https://opensource.suse.com/bci-docs/guides/container-suseconnect/). |
| 70 | + |
28 | 71 |
|
29 | 72 | ## Licensing |
30 | 73 |
|
|
0 commit comments