starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Case Sensitivity Issue with CT Naming in Advanced Settings #101

New Issue
Closed
opened 2026-02-04 16:37:22 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 16:37:22 +03:00
Owner
Copy Link

Originally created by @ali2key on GitHub (Nov 24, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

When creating a container (CT) in Proxmox through script > Advanced Settings, the provided CT name is automatically converted to lowercase.

For example:

  • Input Name: CT-107-NGINX
  • Actual Result: ct-107-nginx

Expected Behavior

The CT name should retain the exact casing as provided, e.g., CT-107-NGINX.

Steps to Reproduce

  1. Run script (e.g. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/nginx.sh)")
  2. Select Advanced Settings.
  3. Enter a name in mixed case, e.g., CT-107-NGINX.
  4. Complete the setup process.

Current Behavior

The resulting CT name is lowercased (ct-107-nginx).

Environment

  • Proxmox Version: 8.2.7

Additional Notes

  • The case sensitivity of CT names can be critical for specific use cases, such as standardized naming conventions.
  • If this is an intentional feature, adding an option to preserve the original casing would be beneficial.

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

Expected Behavior

The CT name should retain the exact casing as provided, e.g., CT-107-NGINX.

Steps to Reproduce

  1. Run script (e.g. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/nginx.sh)")
  2. Select Advanced Settings.
  3. Enter a name in mixed case, e.g., CT-107-NGINX.
  4. Complete the setup process.

Current Behavior

The resulting CT name is lowercased (ct-107-nginx).

Originally created by @ali2key on GitHub (Nov 24, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. When creating a container (CT) in Proxmox through script > **Advanced Settings**, the provided CT name is automatically converted to lowercase. For example: - **Input Name**: `CT-107-NGINX` - **Actual Result**: `ct-107-nginx` ### Expected Behavior The CT name should retain the exact casing as provided, e.g., `CT-107-NGINX`. ### Steps to Reproduce 1. Run script (e.g. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/nginx.sh)") 2. Select **Advanced Settings**. 3. Enter a name in mixed case, e.g., `CT-107-NGINX`. 4. Complete the setup process. ### Current Behavior The resulting CT name is lowercased (`ct-107-nginx`). ### Environment - **Proxmox Version**: 8.2.7 ### Additional Notes - The case sensitivity of CT names can be critical for specific use cases, such as standardized naming conventions. - If this is an intentional feature, adding an option to preserve the original casing would be beneficial. ### What settings are you currently utilizing? - [ ] Default Settings - [X] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. ### Expected Behavior The CT name should retain the exact casing as provided, e.g., `CT-107-NGINX`. ### Steps to Reproduce 1. Run script (e.g. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/nginx.sh)") 2. Select **Advanced Settings**. 3. Enter a name in mixed case, e.g., `CT-107-NGINX`. 4. Complete the setup process. ### Current Behavior The resulting CT name is lowercased (`ct-107-nginx`).
OVERLORD added the not a script issuewontdo labels 2026-02-04 16:37:22 +03:00
OVERLORD commented 2026-02-04 16:37:34 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 24, 2024):

Since when has it been possible to treat LXCs in a case-sensitive manner?

LXC container names in Proxmox are always converted to lowercase. Even if you create a container with uppercase letters (e.g., Ubuntu), it will be stored and managed as ubuntu.

Reasons:

  1. Consistency: Proxmox enforces lowercase to avoid conflicts with case-sensitive Linux filesystems.
  2. File paths: Container names are part of the paths (e.g., /etc/pve/lxc/) and are standardized to lowercase for compatibility.
@MickLesk commented on GitHub (Nov 24, 2024): Since when has it been possible to treat LXCs in a case-sensitive manner? LXC container names in Proxmox are always **converted to lowercase**. Even if you create a container with uppercase letters (e.g., `Ubuntu`), it will be stored and managed as `ubuntu`. #### Reasons: 1. **Consistency**: Proxmox enforces lowercase to avoid conflicts with case-sensitive Linux filesystems. 2. **File paths**: Container names are part of the paths (e.g., `/etc/pve/lxc/`) and are standardized to lowercase for compatibility.
OVERLORD commented 2026-02-04 16:37:41 +03:00
Author
Owner
Copy Link

@ali2key commented on GitHub (Nov 28, 2024):

I was specifically referring to the CT name displayed in the Proxmox UI, not the hostname. It's worth noting that it is possible to manually create a CT name with uppercase letters directly in the UI.

Regarding point 2, I disagree with the reasoning. Proxmox refers to VMs/CTs using their IDs, not their names, so I don't believe case sensitivity would cause conflicts in this context.

@ali2key commented on GitHub (Nov 28, 2024): I was specifically referring to the CT name displayed in the Proxmox UI, not the hostname. It's worth noting that it is possible to manually create a CT name with uppercase letters directly in the UI. Regarding point 2, I disagree with the reasoning. Proxmox refers to VMs/CTs using their IDs, not their names, so I don't believe case sensitivity would cause conflicts in this context.
OVERLORD commented 2026-02-04 16:37:45 +03:00
Author
Owner
Copy Link

@ali2key commented on GitHub (Nov 28, 2024):

Since when has it been possible to treat LXCs in a case-sensitive manner?

LXC container names in Proxmox are always converted to lowercase. Even if you create a container with uppercase letters (e.g., Ubuntu), it will be stored and managed as ubuntu.

Reasons:

  1. Consistency: Proxmox enforces lowercase to avoid conflicts with case-sensitive Linux filesystems.
  2. File paths: Container names are part of the paths (e.g., /etc/pve/lxc/) and are standardized to lowercase for compatibility.

I was specifically referring to the CT name displayed in the Proxmox UI, not the hostname. It's worth noting that it is possible to manually create a CT name with uppercase letters directly in the UI.

Regarding point 2, I disagree with the reasoning. Proxmox refers to VMs/CTs using their IDs, not their names, so I don't believe case sensitivity would cause conflicts in this context.

@ali2key commented on GitHub (Nov 28, 2024): > Since when has it been possible to treat LXCs in a case-sensitive manner? > > LXC container names in Proxmox are always **converted to lowercase**. Even if you create a container with uppercase letters (e.g., `Ubuntu`), it will be stored and managed as `ubuntu`. > > #### Reasons: > 1. **Consistency**: Proxmox enforces lowercase to avoid conflicts with case-sensitive Linux filesystems. > 2. **File paths**: Container names are part of the paths (e.g., `/etc/pve/lxc/`) and are standardized to lowercase for compatibility. I was specifically referring to the CT name displayed in the Proxmox UI, not the hostname. It's worth noting that it is possible to manually create a CT name with uppercase letters directly in the UI. Regarding point 2, I disagree with the reasoning. Proxmox refers to VMs/CTs using their IDs, not their names, so I don't believe case sensitivity would cause conflicts in this context.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label not a script issue wontdo
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/ProxmoxVE#101
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?