-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dockerfiles #515
Merged
tilk
merged 4 commits into
kuznia-rdzeni:master
from
lekcyjna123:lekcyjna/update-dockerfiles-19112023
Dec 1, 2023
Merged
Update dockerfiles #515
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,15 +3,40 @@ FROM ubuntu:23.04 | |
RUN apt-get update && \ | ||
DEBIAN_FRONTEND=noninteractive \ | ||
apt-get install -y --no-install-recommends \ | ||
autoconf automake autotools-dev curl python3 bc lsb-release \ | ||
autoconf automake autotools-dev curl python3.11 python3.11-venv python3-pip bc lsb-release \ | ||
libmpc-dev libmpfr-dev libgmp-dev gawk build-essential \ | ||
bison flex texinfo gperf libtool patchutils zlib1g-dev \ | ||
libexpat-dev ninja-build git ca-certificates python-is-python3 && \ | ||
bison flex texinfo gperf libtool patchutils zlib1g-dev device-tree-compiler \ | ||
libexpat-dev ninja-build git ca-certificates python-is-python3 \ | ||
libssl-dev libbz2-dev libreadline-dev libsqlite3-dev libncursesw5-dev xz-utils tk-dev libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev && \ | ||
rm -rf /var/lib/apt/lists/* | ||
|
||
RUN git clone https://github.com/riscv/riscv-gnu-toolchain && \ | ||
RUN git clone --shallow-since=2023.05.01 https://github.com/riscv/riscv-gnu-toolchain && \ | ||
cd riscv-gnu-toolchain && \ | ||
git checkout 2023.05.14 && \ | ||
./configure --with-multilib-generator="rv32i-ilp32--a*zifence*zicsr;rv32im-ilp32--a*zifence*zicsr;rv32ic-ilp32--a*zifence*zicsr;rv32imc-ilp32--a*zifence*zicsr;rv32imfc-ilp32f--a*zifence;rv32i_zmmul-ilp32--a*zifence*zicsr;rv32ic_zmmul-ilp32--a*zifence*zicsr" && \ | ||
make -j$(nproc) && \ | ||
cd / && rm -rf riscv-gnu-toolchain | ||
|
||
RUN git clone --shallow-since=2023.10.01 https://github.com/riscv-software-src/riscv-isa-sim.git spike && \ | ||
cd spike && \ | ||
git checkout eeef09ebb894c3bb7e42b7b47aae98792b8eef79 && \ | ||
mkdir build/ install/ && \ | ||
cd build/ && \ | ||
../configure --prefix=/spike/install/ && \ | ||
make -j$(nproc) && \ | ||
make install && \ | ||
cd .. && \ | ||
rm -rf build/ | ||
|
||
RUN git clone --depth=1 https://github.com/pyenv/pyenv.git .pyenv && \ | ||
export PATH=/.pyenv/bin:$PATH && \ | ||
export PYENV_ROOT=/root/.pyenv && \ | ||
eval "$(pyenv init --path)" && \ | ||
pyenv install 3.6.15 && \ | ||
pyenv global 3.6.15 && \ | ||
python -V && \ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please remove this line |
||
python -m venv venv3.6 && \ | ||
. venv3.6/bin/activate && \ | ||
python -m pip install --upgrade pip && \ | ||
python -m pip install riscof && \ | ||
pyenv global system |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding your comment #513 (comment) and this change - I don't think that running
apt-get
only in the firstRUN
is that better. Opposite has its benefits - if I wanted to add another tool like spike, with its dependencies I only created next layer that is entirely dedicated to the tool. I didn't modify previous layers, so I didn't need to rebuild the entire container (cached versions of first two steps were used) or upload first two layers again. I would be for this option, as it is useful for updating and developing containers.Are there some benefits of installing everything in first step, that I am missing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a benefit that you don't call
apt update
multiple times, so you generate lower traffic for Debian servers.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But on the other hand, when your are adding new tool with new package dependencies as a new step, instead of installing all of the packages again at rebuild, you use cached previous docker layers and only download the newly added packages, which creates even less traffic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that there is
rm -rf /var/lib/apt/lists/*
in the end of the command. This will make the resulting docker image smaller (by noticeable amount), as all the files that we are going to delete will be ephemeral (and won't exist in the resulting image). If we split that into twoRUN
instructions, the contents of/var/lib/apt/lists/
would be saved as part of the first layer (each instruction is a new layer).