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
Also, does it make sense for cyclops to use layers already in the cache? Switching cyclops to use a docker build call instead of docker run would speed up the build at the cost of aggressive cache usage.
The text was updated successfully, but these errors were encountered:
This means that issuing :run foo is equivalent to a line in dockerfile
"RUN foo", and the cache should be leveraged in either direction by
the docker daemon. Tested in cyclops -> docker build. Unsure of
desired behavior within the repl (should cache be disabled in repl?)
Addresses #41.
Currently, layers generated by cyclops aren't used by other builds, due to differences in the resulting container config:
Also, does it make sense for cyclops to use layers already in the cache? Switching cyclops to use a docker build call instead of docker run would speed up the build at the cost of aggressive cache usage.
The text was updated successfully, but these errors were encountered: