New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when network is set to "none", rancher ignores "hostname" parameter #3492
Comments
There was an error in v0.56.x with hostname that's being corrected in the next release. I will look into whether or not it's relevant to this issue. |
Thanks. If you need testing/validation/etc let me know. |
Verified in v0.58.0-rc2 that this is a bug. If it's not allowed, then the UI should not allow you to select "None" for network and pick your hostname. |
I don't understand the above. Network "none" should always be an option, and hostname matters and is allowed, even if network=none |
@deniseschannon if the fix is needed, most likely it has to be made on python-agent side. The field gets set correctly in the API |
Fixed. To test:
|
Tested with latest build from master: Created container in rancher UI with network mode set to "none" and host name set . Docker inspect for the container shows hostname set to hostname set.
|
I have a new service I set up using docker-compose or the UI. If I set networking to "none", but add a custom hostname, Rancher ignores the custom hostname setting and instead uses the container ID as the hostname in the host.
This is not a docker issue. I tried running a container directly using
docker --net=none --hostname=myhostname
and it respects the hostname, setting it correctly in/etc/hostname
.The text was updated successfully, but these errors were encountered: