Changing Docker Images Safely on GlassHosting Panel
High-level only
Some services allow selecting a different runtime image (Java version, OS tooling). On GlassHosting this is powerful and dangerous: an incompatible image can prevent boot.
Safe practice
- Backup first
- Record the current image/version label
- Change image only when docs or support recommend it for your game version
- Start and verify console health
- Revert to the previous image if the process crashes immediately
When unsure
Open a GlassHosting ticket before experimental image swaps on a production SMP. Prefer supported defaults for Glass Gaming communities.
Measure before you guess
Open the resource graphs on panel.glasshosting.com during a normal play window and during a busy one. Write down approximate CPU and memory percentages alongside how the game felt. That habit turns vague “it lags” reports into actionable upgrades or config tweaks.
If graphs look calm while players stutter, ask whether the issue is client FPS, wifi, or a single loaded farm chunk. If graphs are pegged, stop adding content packs until you either tune view distance/entities or upgrade the GlassHosting plan from the client area.
When to involve GlassHosting support
Open a ticket from billing.glasshosting.com when the platform itself looks wrong: panel cannot start the process, allocations seem missing, or multiple unrelated networks cannot reach the service. Include service name, timestamps, and console excerpts without secrets.
For game-logic questions (plugin conflicts, datapack design), include what you already tried. Skim related knowledgebase articles first—many “outages” are EULA flags, edition mismatches, or whitelist misses.
Operational rhythm that saves weekends
Successful GlassHosting communities treat the panel like a workshop, not a mystery box. Pick one admin who owns updates, one who owns whitelist/ops hygiene, and agree that no one installs experimental jars on Friday night before a big session. Put the panel URL, billing URL, and a short runbook in a private Discord pin so substitutes can help if the main admin is traveling.
When something breaks, capture the first error line from the console, note the time in America/New_York if that is your community timezone, and avoid changing five settings at once. Managed hosting from GlassHosting already removes router and power variables—your job is change control and clear communication with players.
Backup discipline (repeat until boring)
Create a named backup before every risky change: version upgrades, mod installs, permission overhauls, or world-edit events. Download a copy of irreplaceable worlds over SFTP to your PC at least occasionally so you are not relying on a single storage location. After a restore, verify spawn, inventories, and plugin folders before declaring victory in Discord.
GlassHosting makes backups accessible in the panel—use them. A backup you never tested is only a hopeful file. Once per season, restore to confirm the process while the stakes are low.
Quality bar
Definition of done for any change: server starts clean, two players join, critical plugins load, and a fresh backup exists. If any checkbox fails, roll back before opening the gates wider.
Quality bar
Definition of done for any change: server starts clean, two players join, critical plugins load, and a fresh backup exists. If any checkbox fails, roll back before opening the gates wider.
Related links: panel.glasshosting.com · billing.glasshosting.com · glasshosting.com.
