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
I'm just starting to learn docker, so I may be wrong.
However, I saw a docker tutorial on youtube that seemed to say
RUN rm -f /var/www/html/includes/settings.php
doesn't really delete anything;
just creates a new layer on top,
leaving the old file in place in a 'hidden' layer.
Which hackers can find pretty easy.
I think a .dockerignore file is more what we want.
Don't copy the files in to start with.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm just starting to learn docker, so I may be wrong.
However, I saw a docker tutorial on youtube that seemed to say
RUN rm -f /var/www/html/includes/settings.php
doesn't really delete anything;
just creates a new layer on top,
leaving the old file in place in a 'hidden' layer.
Which hackers can find pretty easy.
I think a .dockerignore file is more what we want.
Don't copy the files in to start with.
.dockerignore contents:
.git
includes/settings,php
*.md
etc.
Beta Was this translation helpful? Give feedback.
All reactions