-
Notifications
You must be signed in to change notification settings - Fork 15
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
Workflow fixes #629
Workflow fixes #629
Changes from all commits
eae166b
3a97bde
053684a
5ea4e8d
c4dce92
d271bad
9f47635
ae144d8
c71dfea
709ac8b
4e66913
cdb29f8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -664,6 +664,10 @@ RUN if [ "${NGEN_WITH_PYTHON}" == "ON" ]; then \ | |
fi | ||
USER ${USER} | ||
|
||
ENV VIRTUAL_ENV=/dmod/venv | ||
RUN python3 -m venv $VIRTUAL_ENV && pip3 install numpy | ||
ENV PATH="$VIRTUAL_ENV/bin:$PATH" | ||
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. Hmmm, I assume you are adding this to 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. Basically, something weird seems to be going on, probably after NOAA-OWP/ngen#755, that's breaking the image build. See CIROH-UA/NGIAB-HPCInfra#12 and CIROH-UA/NGIAB-CloudInfra#137 for more details on this specifically, as others are running into it also. 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. Thanks for linking those related issues. Seems like something to do with using a non-virtual environment. My main concern is making it really clear that we are using a virtual environment in the image without needing to come and read the 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. Fair point. I've opened #630. I don't really want to move away from the default environment, but it seems necessary. But I'd like to eventually take this out, once the underlying ngen build issues are resolved. 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. Yeah, this is super weird. Lets just move ahead like you are suggesting and revisit this when we have a fix. |
||
|
||
RUN cd ${BOOST_ROOT} \ | ||
aaraney marked this conversation as resolved.
Show resolved
Hide resolved
|
||
&& tar -xf boost_tarball.blob --strip 1 \ | ||
&& rm boost_tarball.blob \ | ||
|
@@ -843,7 +847,11 @@ RUN cd ${BOOST_ROOT} \ | |
&& chmod +x ${WORKDIR}/entrypoint.sh | ||
|
||
WORKDIR ${WORKDIR} | ||
ENV PATH=${WORKDIR}:${WORKDIR}/bin:$PATH | ||
ENV LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib:/usr/local/lib64:/dmod/shared_libs | ||
# This next value is eventually needed for the t-route build ... | ||
# ... make sure it stays in sync with configure step for netcdf above | ||
ENV NETCDFINC=/usr/include | ||
ENV PATH=/dmod/bin:${WORKDIR}:${WORKDIR}/bin:$PATH:/usr/lib64/mpich/bin | ||
ENV NGEN_PART_EXECUTABLE="${PARTITIONER_EXECUTABLE}" | ||
ENTRYPOINT ["entrypoint.sh"] | ||
|
||
|
@@ -863,6 +871,13 @@ ENV WORKDIR=${WORKDIR} | |
ENV HYDRA_HOST_FILE=/etc/opt/hosts | ||
ENV PATH=${WORKDIR}:${WORKDIR}/bin:/dmod/bin:${PATH}:/usr/lib64/mpich/bin | ||
|
||
ENV LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib:/usr/local/lib64:/dmod/shared_libs | ||
# This next value is eventually needed for the t-route build ... | ||
# ... make sure it stays in sync with configure step for netcdf above | ||
ENV NETCDFINC=/usr/include | ||
ENV VIRTUAL_ENV=/dmod/venv | ||
ENV PATH="$VIRTUAL_ENV/bin:$PATH" | ||
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. similar question as above here. |
||
|
||
#RUN cd ./ngen && mkdir ${WORKDIR}/bin && cp cmake_build/ngen ${WORKDIR}/bin && cp -r data ${WORKDIR}/data \ | ||
# && cd $WORKDIR && rm -rf ngen boost | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
__version__ = '0.8.0' | ||
__version__ = '0.8.1' |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
__version__ = '0.18.0' | ||
__version__ = '0.19.0' |
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.
Is it intentional not to activate the
venv
after creating it here? So, should this instead be: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.
Pretty sure it is effectively active if
VIRTUAL_ENV
is set in the environment (eh, maybePATH
needs updating too, but that's also done).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.
I think that is just used for bookkeeping so that the added
deactivate
shell function can remove$VIRTUAL_ENV
from$PATH
.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.
Here is what an
venv/bin/activate
script looks like (on mac):activate script