https://linear.app/comm/issue/ENG-804/fix-services-images
Moved as much as possible to the parent base image, bumped images' versions.
Depends on D3198
Differential D3268
[services] Move as much content as possible to the parent base image • karol on Feb 23 2022, 8:47 AM. Authored by Tags None Referenced Files
Subscribers
Details https://linear.app/comm/issue/ENG-804/fix-services-images Moved as much as possible to the parent base image, bumped images' versions. Depends on D3198 cd services yarn build-backup-base yarn build-tunnelbroker-base yarn build-blob-base yarn build-backup-base yarn test-blob-service yarn test-backup-service yarn run-tunnelbroker-service
Diff Detail
Event TimelineComment Actions Can you be more precise about what is being "fixed"? I thought that we had some strange situation where either blob depending on backup, or backup depended on blob... but looking at the "before" state here, I can't seem to find where that dependency is... Comment Actions This is done in D3198, here we
I edited the revision's title. Comment Actions Good idea. There are a couple other improvements possible now, in particular building gRPC with the -DgRPC_SSL_PROVIDER=package and -DgRPC_ZLIB_PROVIDER=package flags to avoid building BoringSSL and rebuilding zlib and instead use the system libs installed in the base image.
Comment Actions
Huh? It's confusing to read this. In D3198 you clearly indicate that the confusing dependency is not addressed – in fact, in that diff you created a Linear task to track that issue (on my request). But now you seem to be indicating that that diff solves the confusing dependency? Honestly, I think the reason for my continued confusion is that you responded to my request to be "more precise" with a total of 12 words. Can you please try again, and this time explain in detail an answer to my question? Here's the question again:
Where is the dependency? Does it still exist? Comment Actions Requesting changes for @jimpo's comment. @karol-bisztyga, I'm pretty sure that the issues around build caching in Docker and the reasoning for merging these RUN commands has been discussed before in diffs that you have been on. See my comment here – it's concerning to me that you missed that whole discussion, and then made this change without doing the appropriate research Comment Actions Here I said:
And by "it" I meant this confusing dependency, this was said in D3198. So, once again:
I see now that the description in this task was probably misleading so I updated it. I hope it's now all clear, I'm not sure what else I can say to put yet more light on this, it looks pretty straightforward to me.
Yes, this is an oversight on my end, sorry, I'm going to fix this. @jimpo thanks for clarifying and catching this! Comment Actions Thanks for this explanation – I understand now!!
|