forked from intel/workload-services-framework
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathDockerfile
More file actions
37 lines (30 loc) · 1.52 KB
/
Dockerfile
File metadata and controls
37 lines (30 loc) · 1.52 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
# dummy
#
# Apache v2 license
# Copyright (C) 2023 Intel Corporation
# SPDX-License-Identifier: Apache-2.0
#
# The last of the first two comment lines defines the docker image name. If the comment
# line starts with #, then the image will be pushed to the docker registry if defined.
# If comment line starts with ##, then the image is a local image and will not be pushed.
# See doc/developer-guide/component-design/dockerfile.md for full documentation.
# You can use any base OS in your workload. Popular choices are ubuntu, debian and alpine.
# Declare the OS ingredient as OS_VER and OS_IMAGE.
ARG OS_VER=3.20.2
ARG OS_IMAGE=alpine
FROM ${OS_IMAGE}:${OS_VER}
# For any major ingredients of the workload, list them as pairs of _VER and _REPO ARGS.
# This will be extracted by the script to the github Wiki in the workload ingredient
# table. You can also use _VER/_PACKAGE, _VER/_IMAGE pairs for the same purpose.
ARG DUMMY_VER=0.9
ARG DUMMY_REPO=https://github.com/dummy/dummy.git
# See QATzip for an example of git cloning a repository with access control.
COPY run_test.sh /
# This is the standarized logs collection sequence. In this example, the logs is the
# standard output but the logs can contain anything relevant to the workload execution.
# The logs are archived together with the workload exit code to a fifo /export-logs.
# Then sleep infinity for logs retrievial.
RUN mkfifo /export-logs
CMD (/run_test.sh; echo $? > status) 2>&1 | tee output.logs && \
echo "status output.logs" > /export-logs && \
sleep infinity