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
Dockle 0.4.10 is reporting /tmp as a suspicious directory:
INFO - DKL-LI-0003: Only put necessary files
--
400 | * unnecessary file : usr/local/share/.cache/yarn/v6/npm-@pm2-io-5.0.0-623cbcaf6fe39375f20ac2e75497477a1b1ec5c5-integrity/node_modules/@pm2/io/docker-compose.yml
401 | * Suspicious directory : tmp
What did you expect to happen?
It makes sense to remove any files in /tmp as part of the container build process, however the /tmp directory itself should always exist in a unix system, there are too many things including system functions that expect that directory to exist. Our developers had started to remove the /tmp directory to appease Dockle which caused issues when the containers tried to start.
What happened instead?
Dockle 0.4.10 reports /tmp as DKL-LI-0003 suspicious directory
The text was updated successfully, but these errors were encountered:
Thank you for your recommendation.
I'll think about it.
tomoyamachi
changed the title
Dockle 0.4.10 reports /tmp as DKL-LI-0003 suspicious directory
Stop alerting /tmp as suspicious directory (DKL-LI-0003)
Feb 12, 2023
Description
Dockle 0.4.10 is reporting /tmp as a suspicious directory:
What did you expect to happen?
It makes sense to remove any files in /tmp as part of the container build process, however the /tmp directory itself should always exist in a unix system, there are too many things including system functions that expect that directory to exist. Our developers had started to remove the /tmp directory to appease Dockle which caused issues when the containers tried to start.
What happened instead?
Dockle 0.4.10 reports /tmp as DKL-LI-0003 suspicious directory
The text was updated successfully, but these errors were encountered: