splunk / splunk/docker-splunk

make splunk-redhat-8 fails due to busybox 404

Open
#608 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
549
Forks
277
Avg merge
3d 9h
Merged PRs (30d)
2

Description

make splunk-redhat-8

#0 386.6 --2023-07-27 15:30:59--  https://busybox.net/downloads/binaries/1.35.0-aarch64-linux-musl/busybox
#0 386.7 Resolving busybox.net (busybox.net)... 140.211.167.122
#0 386.9 Connecting to busybox.net (busybox.net)|140.211.167.122|:443... connected.
#0 387.4 HTTP request sent, awaiting response... 404 Not Found
#0 387.6 2023-07-27 15:31:00 ERROR 404: Not Found.
#0 387.6 
------
Dockerfile:36
--------------------
  35 |     
  36 | >>> RUN mkdir /licenses \
  37 | >>>     && curl -o /licenses/apache-2.0.txt https://www.apache.org/licenses/LICENSE-2.0.txt \
  38 | >>>     && curl -o /licenses/EULA_Red_Hat_Universal_Base_Image_English_20190422.pdf https://www.redhat.com/licenses/EULA_Red_Hat_Universal_Base_Image_English_20190422.pdf \
  39 | >>>     && /install.sh && rm -rf /install.sh
  40 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c mkdir /licenses     && curl -o /licenses/apache-2.0.txt https://www.apache.org/licenses/LICENSE-2.0.txt     && curl -o /licenses/EULA_Red_Hat_Universal_Base_Image_English_20190422.pdf https://www.redhat.com/licenses/EULA_Red_Hat_Universal_Base_Image_English_20190422.pdf     && /install.sh && rm -rf /install.sh" did not complete successfully: exit code: 8
make: *** [Makefile:75: base-redhat-8] Error 1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running make splunk-redhat-8 and read the Dockerfile around line 36, along with the Makefile target base-redhat-8 and the referenced install.sh. Confirm the build failure is caused by the BusyBox download returning 404, and consider the issue done when the target builds successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
build-system, devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.