[go: up one dir, main page]
{ const container = $el; // The div with overflow const item = document.getElementById('sidebar-current-page') if (item) { const containerTop = container.scrollTop; const containerBottom = containerTop + container.clientHeight; const itemTop = item.offsetTop - container.offsetTop; const itemBottom = itemTop + item.offsetHeight; // Scroll only if the item is out of view if (itemBottom > containerBottom - 200) { container.scrollTop = itemTop - (container.clientHeight / 2 - item.offsetHeight / 2); } } })" class="bg-background-toc dark:bg-background-toc fixed top-0 z-40 hidden h-screen w-full flex-none overflow-x-hidden overflow-y-auto md:sticky md:top-16 md:z-auto md:block md:h-[calc(100vh-64px)] md:w-[320px]" :class="{ 'hidden': ! $store.showSidebar }">
Contact support
Reference

CopyIgnoredFile

Table of contents
Note

This check is experimental and is not enabled by default. To enable it, see Experimental checks.

Output

Attempting to Copy file "./tmp/Dockerfile" that is excluded by .dockerignore

Description

When you use the Add or Copy instructions from within a Dockerfile, you should ensure that the files to be copied into the image do not match a pattern present in .dockerignore.

Files which match the patterns in a .dockerignore file are not present in the context of the image when it is built. Trying to copy or add a file which is missing from the context will result in a build error.

Examples

With the given .dockerignore file:

*/tmp/*

❌ Bad: Attempting to Copy file "./tmp/Dockerfile" that is excluded by .dockerignore

FROM scratch
COPY ./tmp/helloworld.txt /helloworld.txt

✅ Good: Copying a file which is not excluded by .dockerignore

FROM scratch
COPY ./forever/helloworld.txt /helloworld.txt