[PR #5] [MERGED] ✨ feat(update-portainer-ce): Preserve current Portainer ports #1

New Issue

saavagebueno · 2025-11-20T04:14:15-05:00

saavagebueno commented

2025-11-20 04:14:15 -05:00

📋 Pull Request Information

Original PR: https://github.com/bigbeartechworld/big-bear-scripts/pull/5
Author: @dragonfire1119
Created: 9/4/2024
Status: ✅ Merged
Merged: 9/6/2024
Merged by: @dragonfire1119

Base: master ← Head: update-portainer-ce-ports

📝 Commits (1)

5f6c154 ✨ feat(update-portainer-ce): Preserve current Portainer ports

📊 Changes

1 file changed (+23 additions, -3 deletions)

View changed files

📝 update-portainer-ce/run.sh (+23 -3)

📄 Description

This change ensures that the new Portainer container is created with the same ports as the
current configuration. It first checks the existing Portainer container to get the
current port mappings, and then uses those values when starting the new container.
This way, clients do not need to update any of their configurations when the Portainer
version is updated.

Summary by CodeRabbit

New Features
- Enhanced flexibility in port mappings for the Portainer container by dynamically retrieving current port settings.
- Default ports set to 8000:8000 and 9443:9443, with adaptability to existing configurations.
Bug Fixes
- Resolved issues with hardcoded port values, ensuring the container starts with the correct mappings based on current settings.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/bigbeartechworld/big-bear-scripts/pull/5 **Author:** [@dragonfire1119](https://github.com/dragonfire1119) **Created:** 9/4/2024 **Status:** ✅ Merged **Merged:** 9/6/2024 **Merged by:** [@dragonfire1119](https://github.com/dragonfire1119) **Base:** `master` ← **Head:** `update-portainer-ce-ports` --- ### 📝 Commits (1) - [`5f6c154`](https://github.com/bigbeartechworld/big-bear-scripts/commit/5f6c15407aa8bb398aeafca182ac8621463158d6) ✨ feat(update-portainer-ce): Preserve current Portainer ports ### 📊 Changes **1 file changed** (+23 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `update-portainer-ce/run.sh` (+23 -3) </details> ### 📄 Description This change ensures that the new Portainer container is created with the same ports as the current configuration. It first checks the existing Portainer container to get the current port mappings, and then uses those values when starting the new container. This way, clients do not need to update any of their configurations when the Portainer version is updated.  ## Summary by CodeRabbit - **New Features** - Enhanced flexibility in port mappings for the Portainer container by dynamically retrieving current port settings. - Default ports set to `8000:8000` and `9443:9443`, with adaptability to existing configurations. - **Bug Fixes** - Resolved issues with hardcoded port values, ensuring the container starts with the correct mappings based on current settings.  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

saavagebueno added the pull-request label 2025-11-20 04:14:15 -05:00

saavagebueno closed this issue

2025-11-20 04:14:15 -05:00

saavagebueno referenced this issue

2025-11-20 04:14:16 -05:00

[PR #1] Update run.sh #5

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/big-bear-scripts#1