Skip to content

Pelican Egg Permission Issue – Breakdown #2098

@OfficialShinu

Description

@OfficialShinu

Current Behavior

Servers created through the Pelican panel fail to start after installation.
During pre-boot, Wings attempts to:
Update configuration files (e.g. server.properties)
Apply ownership to the server root directory
Startup aborts with permission errors.
WebSocket connection closes and the server is marked offline.

The issue occurs:
On fresh installs
Even when “Start server after install” is disabled
Without any manual file uploads
Manually running:
chown -R 999:999 /mnt/server
immediately resolves the issue.

Expected Behavior

Expected Behavior

Servers installed via the panel should:
Have consistent file ownership after installation
Start successfully without manual permission fixes

Wings should be able to:
Modify server.propertie
Chown the server directory during pre-boot
Egg install scripts should leave /mnt/server in a valid state for Pelican’s container user (999:999).

Steps to Reproduce

Steps to Reproduce
Create a new server using a Minecraft (Paper / Fabric) egg
Allow the installation to complete (no manual file uploads).
Attempt to start the server (or allow auto-start).
Observe the server failing during pre-boot with permission errors.
Inspect server files on the node:
ls -l /var/lib/pelican/volumes/<server-uuid>/
Notice files owned byroot:rootinstead of pelican:pelican.

Panel Version

1.0.0-beta30.

Wings Version

v1.0.0-beta21

Games and/or Eggs Affected

Minecraft (Paper / Fabric-based eggs)

Docker Image

ghcr.io/pelican-eggs/yolks:java_21 also happened with 17

Error Logs

https://logs.pelican.dev/bb972fd6

as extra info 
adding "chown -R 999:999 /mnt/server" at the end of the egg install script fixes it

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.

Metadata

Metadata

Assignees

Labels

not confirmedNot yet verified or reproduced by maintainers

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions