Docker启动Nacos报错Could not resolve placeholder ‘NACOS_AUTH_IDENTITY_KEY‘

何同学coding

已于 2025-02-28 11:01:25 修改

阅读量1k

点赞数 8

CC 4.0 BY-SA版权

分类专栏： Bug 文章标签： docker 容器运维

于 2025-02-28 10:11:26 首次发布

本文链接：https://blog.csdn.net/qq_43466788/article/details/145920865

Bug 专栏收录该内容

5 篇文章

订阅专栏

具体报错

docker run nacos时报错，容器启动不起来：

Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder ‘NACOS_AUTH_IDENTITY_KEY’ in value “${NACOS_AUTH_IDENTITY_KEY}”

原因分析

经过查询官方信息：https://nacos.io/zh-cn/blog/announcement-token-secret-key.html

nacos2.2.1版本需要配置NACOS_AUTH_TOKEN、NACOS_AUTH_IDENTITY_KEY以及NACOS_AUTH_IDENTITY_VALUE 这三个属性。

解决办法

docker 启动容器时，设置上面3个属性即可，关于这3个属性的设置：

NACOS_AUTH_IDENTITY_KEY以及NACOS_AUTH_IDENTITY_VALUE获取方式：

通过该jwt秘钥生成可以获取自定义jwt密钥：https://tooltt.com/jwt-encode/

设置好下面3个参数：
在这里插入图片描述
然后编码获得这个jwt token：

根据自己设置的参数，参考下面启动命令，重新启动nacos容器：

docker  run -d --env PREFER_HOST_MODE=hostname --env MODE=standalone --env NACOS_AUTH_ENABLE=true --env NACOS_AUTH_TOKEN=8b92c609089f74db3c5ee04bd7d4d89e8b92c609089f74db3c5ee04bd7d4d89e --env NACOS_AUTH_IDENTITY_KEY=xxx --env NACOS_AUTH_IDENTITY_VALUE=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkYXRhIjpbeyJ4eHgiOiJ5eXkifV0sImlhdCI6MTc0MDY2NjEzNywiZXhwIjoxNzcyMTIxNTk5LCJhdWQiOiIiLCJpc3MiOiIiLCJzdWIiOiIifQ.aBuaVv55ph77kjJKg87ho5oOGqAV_yoXwA5Fzod-Y6k  -p 8848:8848 nacos/nacos-server:v2.2.1

客户端连接失败

虽然我们访问ip:8848/nacos，可以成功进入nacos管理页面（账号密码默认nacos），但是当我们的客服端连接时会报错：

java.util.concurrent.ExecutionException: com.alibaba.nacos.shaded.io.grpc.StatusRuntimeException: UNAVAILABLE: io exception
	at com.alibaba.nacos.shaded.com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:566)
	at com.alibaba.nacos.shaded.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:445)
	at com.alibaba.nacos.common.remote.client.grpc.GrpcClient.serverCheck(GrpcClient.java:196)
	at com.alibaba.nacos.common.remote.client.grpc.GrpcClient.connectToServer(GrpcClient.java:307)
	at com.alibaba.nacos.common.remote.client.RpcClient.reconnect(RpcClient.java:498)
	at com.alibaba.nacos.common.remote.client.RpcClient.lambda$start$2(RpcClient.java:339)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:842)
Caused by: com.alibaba.nacos.shaded.io.grpc.StatusRuntimeException: UNAVAILABLE: io exception
	at com.alibaba.nacos.shaded.io.grpc.Status.asRuntimeException(Status.java:533)
	at com.alibaba.nacos.shaded.io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:515)
	at com.alibaba.nacos.shaded.io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:426)
	at com.alibaba.nacos.shaded.io.grpc.internal.ClientCallImpl.access$500(ClientCallImpl.java:66)
	at com.alibaba.nacos.shaded.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:689)
	at com.alibaba.nacos.shaded.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$900(ClientCallImpl.java:577)
	at com.alibaba.nacos.shaded.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:751)
	at com.alibaba.nacos.shaded.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:740)
	at com.alibaba.nacos.shaded.io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
	at com.alibaba.nacos.shaded.io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
	... 3 common frames omitted
Caused by: com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /192.168.31.165:9848
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:702)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at com.alibaba.nacos.shaded.io.grpc.netty.shaded.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:842)
2025-02-28 10:45:46.748 INFO  com.alibaba.nacos.common.remote.client            :60   com.alibaba.nacos.client.remote.worker                    [03dd3e21-e37e-4126-8870-2271e8309c69_config-0] Fail to connect server, after trying 23 times, last try server is {serverIp = '192.168.31.165', server main port = 8848}, error = unknown
2025-02-28 10:45:46.778 ERROR com.alibaba.nacos.common.remote.client            :99   com.alibaba.nacos.client.Worker                    Send request fail, request = ConfigBatchListenRequest{headers={charset=UTF-8, Client-AppName=unknown, Client-RequestToken=83fc92b1abd41ff34b221e3709298352, Client-RequestTS=1740710746466, exConfigInfo=true}, requestId='null'}, retryTimes = 2, errorMessage = Client not connected, current status:STARTING
2025-02-28 10:45:46.778 ERROR com.alibaba.nacos.client.config.impl.ClientWorker :828  com.alibaba.nacos.client.Worker                    Async listen config change error 
com.alibaba.nacos.api.exception.NacosException: Client not connected, current status:STARTING

这是因为：在启动 Nacos 服务时未映射端口 9848，这可能导致客户端连接失败。

从 Nacos 2.x 版本开始，新增了 gRPC 协议，客户端与服务端之间的通信需要使用端口 9848。

因此，您需要在启动 Nacos 服务时，确保映射端口 9848。

所以如果你还需要连接客户端，请参考下面命令期待nacos：

docker run -d \
  --name nacos \
  --env MODE=standalone \
  --env NACOS_AUTH_ENABLE=true \
  --env NACOS_AUTH_TOKEN=8b92c609089f74db3c5ee04bd7d4d89e8b92c609089f74db3c5ee04bd7d4d89e \
  --env NACOS_AUTH_IDENTITY_KEY=xxx \
  --env NACOS_AUTH_IDENTITY_VALUE=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkYXRhIjpbeyJ4eHgiOiJ5eXkifV0sImlhdCI6MTc0MDY2NjEzNywiZXhwIjoxNzcyMTIxNTk5LCJhdWQiOiIiLCJpc3MiOiIiLCJzdWIiOiIifQ.aBuaVv55ph77kjJKg87ho5oOGqAV_yoXwA5Fzod-Y6k \
  -p 8848:8848 \
  -p 9848:9848 \
  nacos/nacos-server:v2.2.1