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
## Issue Description
When running a Docker container, it exits immediately in non-interactive mode, but runs normally in interactive mode.
## Environment Information-**Operating System**:
```sh
$ system_profiler SPHardwareDataType
Hardware:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: Mac15,6
Model Number: Z1AU002P2CH/A
Chip: Apple M3 Pro
Total Number of Cores: 11 (5 performance and 6 efficiency)
Memory: 36 GB
System Firmware Version: 10151.140.19
OS Loader Version: 10151.140.19
Serial Number (system): F6XLNXJ0V4
Hardware UUID: A3FDC5A7-21BA-5EB4-8C10-FF07A49644BE
Provisioning UDID: 00006030-000E10493C52001C
Activation Lock Status: Enabled
The container should start and run normally in non-interactive mode.
Waiting for Feedback
After submitting the issue, wait for feedback from the open-source community. If there are any further questions or information needed, update the issue accordingly.
By following these steps, you can clearly describe the issue you encountered and provide enough information for the open-source community to diagnose and resolve the problem.
The text was updated successfully, but these errors were encountered:
Issue Description
Steps to Reproduce
Download the Docker image:
Output:
Run the container in interactive mode (works fine):
Inside the container:
The container starts Tugraph normally.
Run the container in detached mode (exits immediately):
Check the container status:
Output:
Check the container logs:
Inspect the container:
Output:
Expected Behavior
The container should start and run normally in non-interactive mode.
Waiting for Feedback
After submitting the issue, wait for feedback from the open-source community. If there are any further questions or information needed, update the issue accordingly.
By following these steps, you can clearly describe the issue you encountered and provide enough information for the open-source community to diagnose and resolve the problem.
The text was updated successfully, but these errors were encountered: