f1649fd7e6
This was missed in earlier checks because nothing is really using these two images. I did consider removing them completely as a result, but having them run tests (and fail) was a good sanity check that what we are doing generally works if set up correctly. These images were not set up correctly so failed. We want to move our base python images to quay.io and then pull those images from there when building gitea-init and jinja-init images. To do that we need to use the container build job set and not the docker build job set. So switch both images over and in the process publish the images to quay.io. Then we can can also consume the base images from quay.io as well. We switch to building with docker now that docker is capable of building with speculative images in single arch builds. Change-Id: Ic4cda82a80806112995ae77a49bf5c7be6654ec6
22 lines
742 B
Docker
22 lines
742 B
Docker
# Copyright 2018 Red Hat, Inc.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
|
|
# Trigger image rebuild - Wed Aug 27 03:05:44 PM UTC 2025
|
|
|
|
FROM docker.io/opendevorg/jinja-init as gitea-init
|
|
|
|
COPY entrypoint.sh /
|
|
|
|
ENTRYPOINT ["/entrypoint.sh"]
|