Container and images are unnecessarily large

[monda07]

The Dockerfile leaves around the installer TGZ internally which is unnecessary.
Once installed by default the management server is turned on which is a significant overhead for a container.
Try to use Alpine instead of an entire CentOS installation

[auswells]

One approach you could poke around at is using multistage builds so the installer isn't included in the final image layers.

Ex:

FROM centos:7 as vector-builder

RUN yum install -y libaio sudo

# Pull in Vector saveset
# This Dockerfile will work with any community linux version that follows this naming convention
ENV VECTOR_ARCHIVE actian-vector-*-community-linux-x86_64*
ENV II_SYSTEM /VectorVW

ADD ${VECTOR_ARCHIVE}.tgz .

# Install Vector
RUN cd $VECTOR_ARCHIVE && ./install.sh -express $II_SYSTEM VW -noad && hostname > /tmp/hostname.build

FROM centos:7
# Docker file for Actian Vector Community Edition
LABEL com.actian.vendor="Actian Corporation" \
      description="Actian Vector Community Edition" \
      maintainer=jeremy.hankinson@actian.com
#TAG actian vector community

# Pull dependencies
RUN yum install -y libaio util-linux-ng sudo

ENV II_SYSTEM /VectorVW

# Copy Vector installation from builder stage
COPY --from=vector-builder $II_SYSTEM $II_SYSTEM
COPY --from=vector-builder /tmp/hostname.build /tmp/

# set environment globally
RUN cp $II_SYSTEM/ingres/.ingVWsh /etc/profile.d/vectorVW.sh

# fix hostname as localhost
RUN source /etc/profile.d/vectorVW.sh && sed -i -e "s,`cat /tmp/hostname.build`,localhost," $II_SYSTEM/ingres/files/config.dat && ingsetenv II_HOSTNAME localhost

# Install Vector control script
RUN ln -s $II_SYSTEM/ingres/utility/dockerctl /usr/local/bin/dockerctl

# Allow external connections
# NOTE: these are instance ID dependent (II_INSTALLATION)
EXPOSE 27832 27839 44223 16902

# Give the actian user a database password to allow for access from outside the container
# Only uncomment this line if you want to allow this
# An alternative, and more secure technique is to do this after the image is created and commit the resulting container.
# That way, the real password isn't embedded in a Dockerfile
#       docker exec -u actian -it vector bash -i -c 'echo "alter user actian with password =actian;commit;\\p\\g"|sql iidbdb'
#       docker commit vector actian/vector:community
# RUN sudo su - actian -c 'ingstart >/tmp/ingstart.out;echo "alter user actian with password =actian;commit;\\p\\g" | sql iidbdb>/tmp/pw.out;ingstop -force >/tmp/ingstop.out||true'

# Allow external locations - uncomment to make these available for use
# Data
VOLUME /VectorVW/ingres/data
# Backup
VOLUME /VectorVW/ingres/ckp
# Journals
VOLUME /VectorVW/ingres/jnl
# TxLog
VOLUME /VectorVW/ingres/log
# Configuration
VOLUME /VectorVW/ingres/files
ENTRYPOINT ["dockerctl"]

This approach drops the size from 1.93GB to 1.59GB. It still needs some work since the actian/demo users don't exist in the final image when it runs. There may also be some additional files that need to be copied over from the builder as well that I'm not aware of.

Just thought I'd share since I've been using the same multistage pattern for another project I'm working on.