You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 3, 2024. It is now read-only.
I'm trying to build CI/CD using provided Dockerfile, however, building docker image fails printing error message below. my guess is that there is something wrong with tar ball. but I'm not sure what it is.
environment
/freedom-e-sdk$ docker build -t sifive-build:1.0 -f ./docker/Dockerfile .
Sending build context to Docker daemon 12.75MB
Step 1/19 : FROM ubuntu:16.04 AS download-tarballs
---> 9ff95a467e45
Step 2/19 : ARG SIFIVE_TOOLS_URL=https://static.dev.sifive.com/dev-tools/freedom-tools/v2020.08
---> Using cache
---> 00e3b86421d0
Step 3/19 : ARG RISCV_TOOLS_TARBALL=riscv64-unknown-elf-gcc-10.1.0-2020.08.2-x86_64-linux-ubuntu14.tar.gz
---> Using cache
---> 94cc15539afe
Step 4/19 : ARG RISCV_SEGGER_LIBC_TARBALL=segger_libc-2020.08.2.tar.bz2
---> Using cache
---> 118b67f11e76
Step 5/19 : ARG QEMU_TARBALL=riscv-qemu-5.1.0-2020.08.1-x86_64-linux-ubuntu14.tar.gz
---> Using cache
---> ad8b21ce0f1c
Step 6/19 : RUN apt-get update && apt-get upgrade -y && apt-get install -y bzip2 rsync wget
---> Using cache
---> 6a79e93f6f8c
Step 7/19 : RUN wget --no-verbose ${SIFIVE_TOOLS_URL}/${RISCV_TOOLS_TARBALL} && tar xzf ${RISCV_TOOLS_TARBALL} && mkdir -p /tools && rsync -a ${RISCV_TOOLS_TARBALL%.tar.gz}/* /tools/
---> Using cache
---> 879098681049
Step 8/19 : COPY ./segger-libc/${RISCV_SEGGER_LIBC_TARBALL} ./
COPY failed: file not found in build context or excluded by .dockerignore: stat segger-libc/segger_libc-2020.08.2.tar.bz2: file does not exist
The text was updated successfully, but these errors were encountered:
I'm trying to build CI/CD using provided
Dockerfile
, however, building docker image fails printing error message below. my guess is that there is something wrong with tar ball. but I'm not sure what it is.The text was updated successfully, but these errors were encountered: