Preparing a Custom Image

Prerequisites:

  • A container registry to store and pull your custom image from (Red Hat Quay, AWS ECR, Docker Hub, Google GCR, etc)

Pull the latest Ascend production Spark image

Ascend uses Quay.io to host built Spark images. To download the latest images used in your environment:

  1. Visit https://quay.io/repository/ascendio/pyspark?tab=tags
  2. In the "Filter Tags" search box on the right side, enter "production"
A list of production Ascend imagesA list of production Ascend images

A list of production Ascend images

  1. Pull the image using docker. For example, docker pull quay.io/ascendio/pyspark:production-io.ascend-spark_2.12-3.1.0-SNAPSHOT

Understand the Ascend image file organization (optional)

This section is optional and only needed if you want to add custom scripts to the image for use in your dataflows.

Bash into a running container

  1. Copy the ID of image you just pulled (can be viewed via docker image ls
  2. Run docker run -it --rm <IMAGE_ID> bash
  3. Run cd /app in bash

The /ascend directory

  1. Run echo $PYTHONPATH, and you can see /app is in the Python path. Under /app, the directory /ascend contains some utility functions and connection definitions. This enables you to do things like from ascend.log import logger which print out debugging information in Pyspark Transforms.
  2. To add your own utility functions, we suggest placing them in a directory under /app, which forms a structure like:
app/
      ascend/
      my_organization/
  1. To automate the process, use a Dockerfile, create the needed directory and copy files in.

Build image with new Python libraries

As an example, we would like to install the popular arrow library to manipulate dates and timestamps.

  1. Create a new directory from anywhere in your system.
mkdir test && cd test/
  1. Create a Dockerfile in the directory with the following content:
FROM quay.io/ascendio/pyspark:production-io.ascend-spark_2.12-3.1.0-SNAPSHOT
RUN pip install arrow

Remember to change the image tag to the one you previously pulled.

  1. Build the new image
docker build -t spark_image:prod .

Push the built image to your container registry

  1. Tag the new image with registry's host name and port (refer to your registry's instructions)
    For example, using quay.io, do:
docker image tag spark_image:prod quay.io/my_company/spark_image:prod
  1. Push the tagged image to registry
docker push quay.io/my_company/spark_image:prod

📘

Keeping your image up to date

Ascend releases new Spark images when we add new functionality or change existing implementations. This is typically done on a weekly basis.
It is recommended to regularly rebuild and push your images against the latest Ascend images, to enjoy the latest features.

Summary

In this tutorial, we walked through the end to end process to acquiring and extending Ascend's native Spark images. In the next section, we will demonstrate how to build Transforms using the newly generated image in Ascend.


Did this page help you?