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
The current Docker configuration and logging setup for DICOMHawk have several limitations that impact security, reliability, and maintainability. This issue proposes a series of enhancements to address these limitations and improve the overall robustness of the system.
Proposed Solution:
Running as a non-Root user:
Modify the Dockerfile to create a non-root user and run the application as this user to enhance security.
Binding to All Interfaces:
Change the binding address in dicomhawk.py to 0.0.0.0 to listen on all network interfaces, ensuring the DICOM server is accessible from both inside and outside the container.
Corrected Volume Mappings:
Update the docker-compose.yml file to ensure that logs and other sensitive directories are correctly shared between the host and the containers.
The text was updated successfully, but these errors were encountered:
The current Docker configuration and logging setup for DICOMHawk have several limitations that impact security, reliability, and maintainability. This issue proposes a series of enhancements to address these limitations and improve the overall robustness of the system.
Proposed Solution:
Running as a non-Root user:
Modify the Dockerfile to create a non-root user and run the application as this user to enhance security.
Binding to All Interfaces:
Change the binding address in dicomhawk.py to 0.0.0.0 to listen on all network interfaces, ensuring the DICOM server is accessible from both inside and outside the container.
Corrected Volume Mappings:
Update the docker-compose.yml file to ensure that logs and other sensitive directories are correctly shared between the host and the containers.
The text was updated successfully, but these errors were encountered: