amd64/sl Docker 镜像 - 轩辕镜像 | Docker 镜像高效稳定拉取服务

Note: this is the "per-architecture" repository for the amd64 builds of the sl official image -- for more information, see "Architectures other than amd64?" in the official images documentation and "An image's source changed in Git, now what?" in the official images FAQ.

DEPRECATION NOTICE

Scientific Linux reached end of life June 30, 2024

Quick reference

• Maintained by:
  Scientific Linux Development Team

• Where to get help:
  SL Faq or Email Lists

Supported tags and respective Dockerfile links

WARNING: THIS IMAGE IS NOT SUPPORTED ON THE amd64 ARCHITECTURE

![amd64/sl build status badge]([***]

Quick reference (cont.)

• Where to file issues:
  [***]

• Supported architectures: (more info)
  No supported architectures

• Published image artifact details:
  repo-info repo's repos/sl/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images repo's library/sl label
  official-images repo's library/sl file (history)

• Source of this description:
  docs repo's sl/ directory (history)

Scientific Linux

!logo

These images contain Scientific Linux.

About Scientific Linux

Scientific Linux is a Fermilab sponsored project. Our primary user base is within the High Energy and High Intensity Physics community. However, our users come from a wide variety of industries with various use cases all over the globe – and sometimes off of it!

Our Mission:

Driven by Fermilab's scientific mission and focusing on the changing needs of experimental facilities, Scientific Linux should provide a world class environment for scientific computing needs.

Scientific Linux is a rebuild of Red Hat Enterprise Linux (property of Red Hat Inc. NYSE:RHT).

Please see About Scientific Linux and Why Make Scientific Linux for more information.

Container Tags

A tag will be provided for each of the maintained major releases of Scientific Linux (6, 7).

The latest tag will track the highest version numbered release of Scientific Linux.

Updated images will be released roughly once per month.

Build Process

The root filesystem for these docker images is built on our internal build system.

Docker, overlayfs, and yum

Recent Docker versions support the overlayfs backend, which is enabled by default on most distros supporting it from Docker 1.13 onwards. On SL 6 and 7, that backend requires yum-plugin-ovl to be installed and enabled, which it is in our containers. Make it sure you retain the plugins=1 option in /etc/yum.conf if you update that file; otherwise, you may encounter errors related to rpmdb checksum failure - see Docker ticket *** for more details.

Example Usage

You can try out the containers via:

console
$ docker pull amd64/sl
$ docker run -it amd64/sl:6 cat /etc/redhat-release
$ docker run -it amd64/sl:7 cat /etc/redhat-release

Enabling systemd in SL7

The SL7 docker container ships with systemd mostly functional. You can build a SL7 systemd enabled container with the following Dockerfile.

In order to run a container with systemd, you will need to mount the cgroups volumes from the host.

Dockerfile
# Example SL7 systemd Dockerfile
FROM amd64/sl:7
ENV container docker
### This example enables httpd via systemd within the container
RUN yum -y install httpd && yum clean all && systemctl enable httpd.service
EXPOSE 80
### End of example commands for httpd via systemd
VOLUME [ "/sys/fs/cgroup" ]
CMD ["/usr/sbin/init"]

You can build and run this example (with apache) via:

console
$ docker build --rm -t local/mycontainer your/path
$ docker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 80:80 local/mycontainer

Which will run systemd within the container in a limited context.

It is recommended that you install any relevant OCI hooks for your container host - such as oci-register-machine or oci-systemd-hook.

Some container hosts must add --tmpfs /run to the docker run command.

License

By default the SL docker images do not include documentation or license files. If you require them, please remove tsflags=nodocs from /etc/yum.conf and run yum reinstall mypackage to recieve the documentation.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's sl/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.