starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-05-04 18:00:48 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

Internal server error when using Docker labels with a period #360

New Issue
Closed
opened 2026-02-05 17:29:27 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 17:29:27 +03:00
Owner
Copy Link

Originally created by @cbrl on GitHub (Jun 12, 2025).

Current Behavior

Adding/modifying a docker label with a period results in an internal server error.

For example, attempting to work with the label test.label with a description of content results in the exception No synthesizer found for key: "content". This occurs at app/Http/Middleware/LanguageMiddleware.php:22.

Here is the request body reported in the error after trying to edit the label described above:

{
    "_token": "<truncated>",
    "components": [
        {
            "snapshot": "<truncated>",
            "updates": {
                "data.docker_labels.test.label": "content",
                "data.docker_labels.test": "__rm__",
                "data.docker_labels": {
                    "test.label": "content"
                }
            },
            "calls": []
        }
    ]
}

Interestingly, this doesn't actually appear to prevent the usage of these labels. I can add and remove labels with periods and see the changes reflected in the container as expected.

Expected Behavior

No error is thrown.

According to https://docs.docker.com/engine/manage-resources/labels/#key-format-recommendations, valid docker labels may contain alphanumeric characters, periods, underscores, slashes, and hyphens. Only periods cause this issue.

Steps to Reproduce

Attempt to add/edit a docker label with a period in it on any server.

Panel Version

v1.0.0-beta21

Wings Version

v1.0.0-beta13

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Originally created by @cbrl on GitHub (Jun 12, 2025). ### Current Behavior Adding/modifying a docker label with a period results in an internal server error. For example, attempting to work with the label `test.label` with a description of `content` results in the exception `No synthesizer found for key: "content"`. This occurs at `app/Http/Middleware/LanguageMiddleware.php:22`. Here is the request body reported in the error after trying to edit the label described above: ```json { "_token": "<truncated>", "components": [ { "snapshot": "<truncated>", "updates": { "data.docker_labels.test.label": "content", "data.docker_labels.test": "__rm__", "data.docker_labels": { "test.label": "content" } }, "calls": [] } ] } ``` Interestingly, this doesn't actually appear to prevent the usage of these labels. I can add and remove labels with periods and see the changes reflected in the container as expected. ### Expected Behavior No error is thrown. According to https://docs.docker.com/engine/manage-resources/labels/#key-format-recommendations, valid docker labels may contain alphanumeric characters, periods, underscores, slashes, and hyphens. Only periods cause this issue. ### Steps to Reproduce Attempt to add/edit a docker label with a period in it on any server. ### Panel Version v1.0.0-beta21 ### Wings Version v1.0.0-beta13 ### Games and/or Eggs Affected _No response_ ### Docker Image _No response_ ### Error Logs ```bash ``` ### Is there an existing issue for this? - [x] I have searched the existing issues before opening this issue. - [x] I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server. - [x] I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
OVERLORD commented 2026-02-05 17:29:33 +03:00
Author
Owner
Copy Link

@rmartinoscar commented on GitHub (Jun 12, 2025):

Hey are you able to produce on the demo ?
I thought i resolved it in https://github.com/pelican-dev/panel/pull/1261

@rmartinoscar commented on GitHub (Jun 12, 2025): Hey are you able to produce on the [demo](https://demo.pelican.dev) ? I thought i resolved it in https://github.com/pelican-dev/panel/pull/1261
OVERLORD commented 2026-02-05 17:29:36 +03:00
Author
Owner
Copy Link

@cbrl commented on GitHub (Jun 12, 2025):

I do see that behavior in the demo too. It doesn't seem to happen reliably though. It appears most reliable when erasing a trailing period, but I don't know if that's actually a clue since I've also seen it happen when editing the label in any other manner.

@cbrl commented on GitHub (Jun 12, 2025): I do see that behavior in the demo too. It doesn't seem to happen reliably though. It appears most reliable when erasing a trailing period, but I don't know if that's actually a clue since I've also seen it happen when editing the label in any other manner.
OVERLORD commented 2026-02-05 17:29:39 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Jun 12, 2025):

Can reproduce.
It happens when you edit a server with a . in the docker labels and you try to remove the . from the label. The error is thrown right after the input is updated and before you even hit save.

Image
Image

@Boy132 commented on GitHub (Jun 12, 2025): Can reproduce. It happens when you edit a server with a `.` in the docker labels and you try to remove the `.` from the label. The error is thrown right after the input is updated and before you even hit save. ![Image](https://github.com/user-attachments/assets/4fe68c35-1916-4e7a-8159-ac7aadb68520) ![Image](https://github.com/user-attachments/assets/88ff4e16-f3f1-4f8d-aa7d-093e45f8a7b0)
OVERLORD commented 2026-02-05 17:29:40 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Aug 14, 2025):

This will be fixed when updating to filament v4.

@Boy132 commented on GitHub (Aug 14, 2025): This will be fixed when updating to filament v4.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#360
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?