You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{"level":"warn","ts":"2025-03-20T09:33:23.866545Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:63","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0002da5a0/127.0.0.1:2379","attempt":0,"error":"rpc error: code = InvalidArgument desc = etcdserver: user name is empty"}
Error: etcdserver: user name is empty
Additional information
I also tried manually setting the ETCD_DAEMON_USER and ETCD_DAEMON_GROUP, but to no avail.
I found that helm has this argument of --set auth.rbac.create=false. Is there anything like this that I could add to Portainer somewhere?
The text was updated successfully, but these errors were encountered:
Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.
If you think that's not the case and would like to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Please don't hesitate to contact us if you have any questions or need help.
Suppose you have questions about the application, customizing its content, or using technology and infrastructure. In that case, we strongly recommend that you consult the forums and user guides provided by the project responsible for the application or technology.
With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.
Name and Version
bitnami/etcd:latest
What architecture are you using?
amd64
What steps will reproduce the bug?
ALLOW_NONE_AUTHENTICATION=yes
andETCD_ROOT_PASSWORD
/bin/sh/
terminal and set theENDPOINT
What is the expected behavior?
What do you see instead?
Additional information
I also tried manually setting the
ETCD_DAEMON_USER
andETCD_DAEMON_GROUP
, but to no avail.I found that helm has this argument of
--set auth.rbac.create=false
. Is there anything like this that I could add to Portainer somewhere?The text was updated successfully, but these errors were encountered: