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
COPY fails, if there is at least one file in the OracleDatabase/SingleInstance/extensions/prebuiltdb/setup directory:
Step 15/16 : COPY --chown=oracle:dba setup/* "$ORACLE_BASE"/scripts/extensions/setup
When using COPY with more than one source file, the destination must be a directory and end with a /
It does succeed, if the OracleDatabase/SingleInstance/extensions/prebuiltdb/setup directory is empty, as in that case, no copying occurs at all.
Bug trigger
./buildExtensions.sh -x 'prebuiltdb'
,OracleDatabase/SingleInstance/extensions/prebuiltdb/setup
,AUTO_MEM_CALCULATION
.Note that the extra build args are not required to trigger the bug - but they are required for setups which enable
AUTO_MEM_CALCULATION
.As detailed in the
prebuiltdb/README.md
, BuildKit is disabled in order to be able to use the--memory
build argument.Reproduction note
Note that
--memory
is only available withDOCKER_BUILDKIT=0
.The
Dockerfile
reference describes:However, the lack of a trailing slash in the
COPY
destination directory does not cause a fatal error when using BuildKit.But with the legacy builder it does cause a fatal error - see section "Actual result" below.
We cannot use BuildKit as long as equivalents of
--memory
andcpuset-cpus
are not supported.Expected result
COPY
succeeds:Actual result
COPY
fails, if there is at least one file in theOracleDatabase/SingleInstance/extensions/prebuiltdb/setup
directory:It does succeed, if the
OracleDatabase/SingleInstance/extensions/prebuiltdb/setup
directory is empty, as in that case, no copying occurs at all.Fixing the bug
Add the missing slash:
The text was updated successfully, but these errors were encountered: