Allow manual setting of slave name#195
Allow manual setting of slave name#195chriselsen wants to merge 2 commits intolinuxserver:masterfrom
Conversation
Allow manual setting of slave name via "SLAVE_NAME" env variable, as e.g. ECS with Fargate does not support setting the hostname of a container (task).
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thanks for opening this pull request! Be sure to follow the pull request template!
|
I am a bot, here are the test results for this PR:
|
|
I am a bot, here are the test results for this PR:
|
|
I am a bot, here are the test results for this PR:
|
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This pull request is locked due to inactivity |
2 participants
Allow manual setting of slave name via "SLAVE_NAME" env variable, as e.g. ECS with Fargate does not support setting the hostname of a container (task).
Description:
Allow manual setting of slave name via "SLAVE_NAME" env variable, as e.g. ECS with Fargate does not support setting the hostname of a container (task).
Benefits of this PR and context:
Allow manual setting of slave name via "SLAVE_NAME" env variable, as e.g. ECS with Fargate does not support setting the hostname of a container (task).
How Has This Been Tested?
Tested in custom container image with implemented change on ECS with Fargate.
Source / References:
N/A