-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panel inside Docker not writing to log file #4838
Labels
bug
Something that's not working as it's intended to be.
Comments
davemsh
added
the
not confirmed
Report seems plausible but requires additional testing or 3rd part confirmation.
label
Aug 12, 2023
This is a known issue with the image. Until it's addressed the suggested fix is |
The workaround worked, thanks! |
I'll have a pr to fix this today |
matthewpi
added
bug
Something that's not working as it's intended to be.
and removed
not confirmed
Report seems plausible but requires additional testing or 3rd part confirmation.
labels
Aug 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
I've got Panel running using the official Docker image (
ghcr.io/pterodactyl/panel:v1.11.3
) on Ubuntu Server 22.04 host system, but there seems to be an issue with how the provided Docker Compose yml is mounting the logs path.The problem is that nothing gets logged. Nothing at all. The Laravel log file gets created, but nothing gets written to it, aside from a single message that only occurs on initial container creation that says the following:
[2023-08-12 03:12:25] production.NOTICE: A query exception was encountered while trying to load settings from the database: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'panel.settings' doesn't exist (SQL: select * from `settings`)
After this message, nothing ever gets logged afterward, so long as the logs folder is mounted in Docker.
If I comment out the line where the logs folder gets mounted (
/srv/pterodactyl/logs/:/app/storage/logs
), it works fine, but then the logs aren't visible without going into the container's terminal.Expected Behavior
Logs are properly written to the mounted folder path.
Steps to Reproduce
Run a fresh instance of Panel on Docker using the example Docker Compose.
Panel Version
1.11.3
Wings Version
N/A, haven't set that up yet
Games and/or Eggs Affected
No response
Docker Image
ghcr.io/pterodactyl/panel:v1.11.3
Error Logs
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: