jboss-dockerfiles / base

Base image for all JBoss community Docker images

Base Docker image for JBoss community projects

This repository contains base image that is used to build the portfolio of Docker images for JBoss community projects.

Base image

This image is used as a base image for all JBoss community images. It provides a base layer that includes:

1. A jboss user (uid/gid 1000) with home directory set to /opt/jboss
2. A few tools that may be useful when extending the image or installing software, like unzip.

Operating system

This image uses CentOS 7.

Working directory

This image has the working directory set to /opt/jboss, which is the jboss user home directory at the same time.

Availability

The Dockerfile is available in the master branch and is built in the Docker HUB as jboss/base:latest.

base's Issues

jboss/base missing 'ss' command

After the change from fedora:20 to centos:7, the base jboss/* image is missing the 'ss' command.
328f451

Strangely enough, it's part of centos:7.

Arquillian Cube is using 'ss' by default to detect when a Service inside a Container is actually started.
arquillian/arquillian-cube#274 (comment)

Permissions on /opt/jboss are too restrictive

$ ls -l /opt/
drwx------. 6 jboss jboss 4096 Jun 26 13:16 jboss

On a restrictive environment like OSE3 this means that no apps can run as they run under an arbitrary UID. Changing this to 755 would be a simple fix.

Vulnerabilities showing up in GCR scan

Severity	CVSS	Fix available	Package	Documentation
Critical	9.3	Yes	Multiple	CVE-2017-16997
High	7.5	Yes	Multiple	CVE-2018-6485
High	7.5	Yes	Multiple	CVE-2018-1000120
High	7.5	Yes	Multiple	CVE-2018-15688
High	7.5	Yes	Multiple	CVE-2018-12910
High	7.5	Yes	Multiple	CVE-2018-18311
High	7.5	Yes	Multiple	CVE-2015-9262
Medium	4.3	Yes	binutils	CVE-2018-7568
Medium	4.3	Yes	binutils	CVE-2018-7569
Medium	4.6	Yes	setup	CVE-2018-1113
Medium	5	Yes	Multiple	CVE-2018-1000007
Medium	6.8	Yes	binutils	CVE-2018-7208
Medium	4.3	Yes	binutils	CVE-2018-13033
Medium	5	Yes	Multiple	CVE-2018-1000121
Medium	6.8	Yes	Multiple	CVE-2018-11236
Medium	4.3	Yes	binutils	CVE-2018-10373
Medium	4.3	Yes	binutils	CVE-2018-10535
Medium	4.3	Yes	Multiple	CVE-2018-13988
Medium	4.3	Yes	Multiple	CVE-2018-10733
Medium	6.8	Yes	binutils	CVE-2018-7643
Medium	5	Yes	Multiple	CVE-2018-10767
Medium	5	Yes	Multiple	CVE-2018-10768
Medium	4.3	Yes	binutils	CVE-2018-8945
Medium	4.3	Yes	Multiple	CVE-2017-18267
Medium	6.4	Yes	Multiple	CVE-2018-1000122
Medium	5	Yes	Multiple	CVE-2018-1061
Medium	4.3	Yes	binutils	CVE-2018-10372
Medium	6.5	Yes	krb5-libs	CVE-2018-5729
Medium	4.3	Yes	binutils	CVE-2018-7642
Medium	4.3	Yes	binutils	CVE-2018-10534
Medium	6.4	Yes	Multiple	CVE-2018-1000301
Medium	5	Yes	Multiple	CVE-2018-1060
Medium	4.6	Yes	Multiple	CVE-2018-11237
Medium	5.5	Yes	krb5-libs	CVE-2018-5730
Unspecified	0	Yes	Multiple	CVE-2019-3815
Unspecified	0	Yes	bind-license	CVE-2018-5742
Unspecified	0	Yes	Multiple	CVE-2018-16864
Unspecified	0	Yes	Multiple	CVE-2018-16865

Request to add an aarch64 branch

I'd like to maintain a copy of this repo build for aarch64. Can you please create a aarch64 branch so I can send you a PR request for https://github.com/KurtStam/base/tree/aarch64.

xmlstarlet

It seems that the latest builds are no longer including xmlstarlet because it isn't in the CentOS repositories, but it was in the Fedora repositories.

The tool is in the EPEL repositories, so one fix is to do the following:

yum install -y epel-release && yum install -y xmlstarlet

Update to CentOS 8?

Hi,

the base image is currently based on CentOS 7. Are there any plans to provide a base image that is based on CentOS 8?

Keycloak Version in a Docker Build is not Clear

It is not very clear which version of Keycloak is actually in each docker image that is packaged on docker hub. It would be nice to know exactly which version of keycloak is in use based tags or image name.

I found it finally by going to
https://github.com/jboss-dockerfiles/keycloak/blob/master/server/Dockerfile

See Microsofts naming convention.
https://hub.docker.com/r/microsoft/dotnet