Closed yanghua closed 9 months ago
@pan3793 I have tested. It seems everything is OK.
FYI. I found this change actually has side effects, it corrupts the docker build cache mechanism.
before this change, performing ./build-image.sh
and again, the second time docker build
hit the cache, but after this change, not.
To be clear, I'm fine with either keeping it or reverting it.
FYI. I found this change actually has side effects, it corrupts the docker build cache mechanism.
before this change, performing
./build-image.sh
and again, the second timedocker build
hit the cache, but after this change, not.To be clear, I'm fine with either keeping it or reverting it.
Do not know why this behavior causes miss cache. Every time, running ./build-image.sh
, the cp
command still prepare the previous files before building images just like we do not remove them.
because the inode changed? not sure.
Close #42