You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using GO SDK, connected to Dagger engine. In one session, firstly run a shell command in container A, and then run a shell command in container B.
I found if the relevant images are big images, when I rerun the program the pull images operations were not cached.
If the containers related are small images like alpine, they are well cached.
Any suggestions to cache big images, it's time consumed.
Here's my environment
SDK: Dagger GO SDK
OS: mac OS
Docker: Docker Desktop 4.20.0 (Engine 24.0.2)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was using GO SDK, connected to Dagger engine. In one session, firstly run a shell command in container A, and then run a shell command in container B.
I found if the relevant images are big images, when I rerun the program the pull images operations were not cached.
If the containers related are small images like alpine, they are well cached.
Any suggestions to cache big images, it's time consumed.
Here's my environment
SDK: Dagger GO SDK
OS: mac OS
Docker: Docker Desktop 4.20.0 (Engine 24.0.2)
Beta Was this translation helpful? Give feedback.
All reactions