Skip to content
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 dockerfile - maint/pre-hnn-core branch #338

Open
wants to merge 11 commits into
base: maint/pre-hnn-core
Choose a base branch
from

Conversation

jashlu
Copy link
Collaborator

@jashlu jashlu commented Nov 7, 2023

No description provided.

@jashlu jashlu changed the title updated dockerfile and plist filename update dockerfile - maint/pre-hnn-core branch Nov 7, 2023
RUN pip install hnn-core

RUN sudo apt-get update && \
sudo apt-get install -y neuron-dev
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, is this preferred over doing a pip installation of NEURON?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just from experience I was having problems installing neuron with pip3, and so from some online resources (https://command-not-found.com/nrnivmodl) I tried an alternative and it worked

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I've never run into issues using pip except on Windows (without WSL). NEURON doesn't currently distribute a python wheel for windows, but it should work for WSL, native linux, and macOS.

Copy link
Collaborator Author

@jashlu jashlu Nov 7, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the error I run into

=> ERROR [19/28] RUN sudo apt-get update &&     sudo apt-get install --no-install-recommends -y         make gcc libc6-dev libtinfo-dev lib  11.0s 
...

9.505 Processing triggers for libc-bin (2.31-0ubuntu9.12) ...
9.545 Cloning into '/home/hnn_user/hnn_source_code'...
10.82 nrnivmodl mod
10.82 make: nrnivmodl: Command not found
10.82 make: *** [Makefile:11: x86_64/special] Error 127

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To further clarify, I run into this error attempting to build the image on my mac

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess the "barebone" mac install in a docker is not the same as an actual mac computer ... there may be some compilers etc missing

@rythorpe
Copy link
Contributor

@jashlu thanks for your work on this. Is it ready for a final review, or is there still more to do?

@jashlu
Copy link
Collaborator Author

jashlu commented Nov 27, 2023

@jashlu thanks for your work on this. Is it ready for a final review, or is there still more to do?

Hi thanks for the reminder, I wasn't sure which one of the two PRs would be merged in, are we updating both the main and maint/pre-hnn-core branches? @rythorpe

@ntolley
Copy link
Contributor

ntolley commented Nov 28, 2023

I think the final decision was to just stick with the docker build for maint/pre-hnn-core as the official version we recommend.

@dylansdaniels perhaps let's discuss in our next meeting updating the website documentation to make this clearer? right now people will be attempting to install a version of HNN-GUI that is fairly unstable as hnn-core continues to change

@rythorpe
Copy link
Contributor

Just to clarify @jashlu, we went ahead and merged your recent docker build changes for master since you already had it working, but still want to encourage users to use the docker build on maint/pre-hnn-core.

@jashlu
Copy link
Collaborator Author

jashlu commented Nov 29, 2023

Just to clarify @jashlu, we went ahead and merged your recent docker build changes for master since you already had it working, but still want to encourage users to use the docker build on maint/pre-hnn-core.

Understood, thanks for the explanation. I will hold off on merging just for a bit while I work through adding the script to simplify one step in the xserver installation, I will tag you guys for re-review when it is done, should be done soon, thanks!

@jashlu jashlu mentioned this pull request Nov 30, 2023
@rythorpe
Copy link
Contributor

rythorpe commented Dec 1, 2023

I'll try to test this out on my windows machine this weekend. Feel free to bug me early next week if I don't get back to you soon @jashlu!

@jashlu
Copy link
Collaborator Author

jashlu commented Dec 1, 2023

I'll try to test this out on my windows machine this weekend. Feel free to bug me early next week if I don't get back to you soon @jashlu!

That would be greatly appreciated, have a great weekend!

@rythorpe
Copy link
Contributor

rythorpe commented Feb 1, 2024

@dylansdaniels I just noticed your comment in #337. Are you fetching from this branch? If not, I believe this the branch we (maint/pre-hnn-core) that we want to be testing and using in the future.

@dylansdaniels-berkeley
Copy link

So I was moreso referring to how if you follow the docker instructions in the pre-hnn-core branch, it will have you clone from hnn.git, which will put you on master branch. And then if you proceed to the next step in the instructions, it'll direct you to ./scripts/configure_vcxsrv.sh, but you won't be on the branch that has that file.

installer/docker/README.md Outdated Show resolved Hide resolved
Co-authored-by: Ryan Thorpe <ryan_thorpe@brown.edu>
@rythorpe
Copy link
Contributor

rythorpe commented Feb 6, 2024

Any other recommendations and/or concerns here @dylansdaniels?

@dylansdaniels
Copy link
Contributor

Sorry for the delay @rythorpe. That covers it in terms things I bumped into doing a fresh install on Windows 11

Copy link
Contributor

@rythorpe rythorpe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dylansdaniels for testing this out! @jashlu, as soon as you feel this is ready on your end, please update the title of this PR to "[MRG]..." to signal that it's on the final stage of review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants