- Newest
- Most votes
- Most comments
I thought it would be cached if privileged mode was enabled.
I also don't think I see anything wrong with the buildspec.yml.
https://docs.aws.amazon.com/codebuild/latest/userguide/build-caching.html
Put the following command in the build phase of buildspec.yml to make sure CodeBuild is not changing hosts.
If the host is different, the cache is not used.
uname -n
https://docs.aws.amazon.com/codebuild/latest/userguide/build-caching.html#caching-local
Local caching stores a cache locally on a build host that is available to that build host only. This is a good option for intermediate to large build artifacts because the cache is immediately available on the build host. This is not the best option if your builds are infrequent. This means that build performance is not impacted by network transfer time.
I'm seeing similar issues. The --cache-from argument does not appear to do anything inside CodeBuild. Have you been able to resolve the issue?
Nope. I have given up on this.
Relevant content
- Accepted Answerasked 8 months ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Do you mean to say, the pre-build and the build stages are actually run in different host instances?
It means that different hosts may have been used in the first and second builds.