-
Notifications
You must be signed in to change notification settings - Fork 0
remove docker container. #460
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
Conversation
|
I made the corresponding changes to |
You're in the right group now. |
thanks! |
msilvafe
left a comment
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.
Let's try it out. Thanks.
|
I don't know of any use of the |
|
associated PR in simonsobs/socs#858 |
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.
This looks to me like it will result in pretty different images. The chain of images as I understand it is: ubuntu:20.04 > smurf-base > smurf-rogue > pysmurf > so_smurf_base > sodetlib > ocs-pysmurf-agent.
This chain installs the following packages (I tried to identify big things, there a bunch of other misc things, including system packages to support building this software, etc.):
- EPICS (and
pyepics) - IMPI package
- FirmwareLoader binary
- ProgramFPGA utility
- Rogue
- SMURF PCIe card software
pysmurfspt3gso3gsotodlibsodetlibsocs
Dropping the sodetlib image and using the socs image with a pip install sodetlib would mean from these you'd only have:
pyepicspysmurfsodetlibsotodlibso3g(with built in spt3g)socs
I don't believe these dependencies would be installed:
- EPICS (Does
pyepicsmean we get this? I don't think it does.) - IMPI package
- FirmwareLoader binary
- ProgramFPGA utility
- Rogue
- SMURF PCIe card software
Are any of these critical for pysmurf-controller operation? If so, then I don't think this will work without further modification to how the pysmurf-controller image is built.
(EDIT: Sorry if you got this twice, made a normal comment accidentally at first. Deleted and made it an official review.)
|
Ah, and now I'm realizing this whole step is building on Time to go make some more coffee... |
BrianJKoopman
left a comment
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.
With simonsobs/socs#858 merged now I think this PR is good to go.
This was missed in #460.
This was missed in #460.
We stopped building the sodetlib image and started installing it directly into the pysmurf controller agent image. See [1] for the removal details. [1] - #460
We stopped building the sodetlib image and started installing it directly into the pysmurf controller agent image. See [1] for the removal details. [1] - #460
We stopped building the sodetlib image and started installing it directly into the pysmurf controller agent image. See [1] for the removal details. [1] - #460
I'm proposing we remove the
sodetlibdocker container. As far as I can tell it is only used to build theocs-pysmurf-agent(here), and we could simply installsodetliband specify a release tag there. The only other reference I have found to this image are indocker-compose.yamlfiles committed to theocs-site-configsrepo for some institutions. In the SAT/LAT configs it has been replaced byocs-pysmurf-agent. We should then also remove theSODETLIB_TAGthat remains in those configs but is unused.This would simplify the release process by removing one layer of docker inheritance, but I appreciate that I may have overlooked other uses of this image (although I did not find any in the
simonsobsorganisation), so please let me know if you think this may be the case.An accompanying PR will be necessary in
socsto installsodetlibin the correspondingDockerfile.