Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

resource.log file is always created,throwing errors on read-only filesystems #5

Open
sam-github opened this issue Feb 21, 2020 · 0 comments

Comments

@sam-github
Copy link

For security, containers should be able to run with a read-only FS, but this package throws errors if it cannot create resourceRegistry.log.

There appears to be some configuration available in

dumper_file: {
type: 'file',
maxLogSize: global.KNJ_MAX_LOG_SIZE,
filename: 'resourceRegistry.log'
}
},
categories: {
default: {
appenders: [
isTrue(process.env.KNJ_LOG_TO_CONSOLE) ? 'knj_restclient_log_console' : 'knj_restclient_log_file'
, but it isn't sufficient.

Even when KNJ_LOG_LEVEL is set to NONE, the file is created (but empty).

Even when KNJ_LOG_TO_CONSOLE is set to true, the file is created.

Is there any other mechanisms to avoid any attempts to write to the local FS?

If not, can you implement one? Perhaps make KNJ_LOG_TO_CONSOLE cause all logging to go to console?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant