我正在尝试健康检查扩展openjdk:8
的容器。可以在https://github.com/jhipster/jhipster-registry/blob/master/Dockerfile找到相应的Dockerfile
我有以下目录结构:
test/
├── central-server-config
│ └── application.yml
├── docker-compose.yml
├── jhipster-registry.yml
└── Ping.jar
application.yml
#common configuration shared between all applications
configserver:
name: Docker JHipster Registry
status: Connected to the JHipster Registry running in Docker
jhipster:
security:
authentication:
jwt:
secret: 3ac0a39ed9a2a58ca74d9d36c5227e51225480e2
eureka:
client:
service-url:
defaultZone: http://admin:${jhipster.registry.password}@jhipster-registry:8761/eureka/
泊坞窗,compose.yml
version: '2.1'
services:
jhipster-registry:
extends:
file: jhipster-registry.yml
service: jhipster-registry
mem_limit: 512m
ports:
- 8761:8761
healthcheck:
test: ["CMD", "java", "-jar", "Ping.jar", "localhost", "8761"]
interval: 30s
retries: 10
jhipster-registry.yml
version: '2.1'
services:
jhipster-registry:
image: jhipster/jhipster-registry:v4.0.2
volumes:
- ./central-server-config:/central-config
# By default the JHipster Registry runs with the "dev" and "native"
# Spring profiles.
# "native" profile means the filesystem is used to store data, see
# http://cloud.spring.io/spring-cloud-config/spring-cloud-config.html
environment:
- SPRING_PROFILES_ACTIVE=dev,native
- SECURITY_USER_PASSWORD=password
- JHIPSTER_REGISTRY_PASSWORD=password
# - GIT_URI=https://github.com/jhipster/jhipster-registry/
# - GIT_SEARCH_PATHS=central-config
ports:
- 8761:8761
ping.Java
package ping;
import java.io.IOException;
import java.net.InetSocketAddress;
import java.net.Socket;
public class Main {
public static void main(String[] args) {
if (args.length != 2) {
System.exit(-1);
}
String host = args[0];
int port = 0;
try {
port = Integer.parseInt(args[1]);
} catch (NumberFormatException e) {
e.printStackTrace();
System.exit(-2);
}
try (Socket socket = new Socket()) {
socket.connect(new InetSocketAddress(host, port), 10 * 1000);
System.exit(0);
} catch (IOException e) {
System.exit(1);
}
}
}
我通过运行启动容器
docker-compose up -d --force-recreate
在测试目录中,我可以通过浏览器访问jhipster-registry。它也可以通过上面的jar程序访问:
izio@1z10:~$ cd Desktop/
izio@1z10:~/Desktop$ java -jar Ping.jar localhost 8761
izio@1z10:~/Desktop$ echo $?
0
izio@1z10:~/Desktop$
返回0,表示可以连接到服务。
如果有人想知道,我也尝试使用curl
但没有成功(几乎可以肯定它没有在docker图像中提供以减小尺寸),所以我切换到这个Java
片段希望没有问题因为它是openjdk ...
使用这种配置,jhipster-registry在大约3分钟内启动,但无论我等待多长时间,它总是显示为health starting
,最后是unhealthy
(在10 x 30''= 300''= 5'之后)。
有什么想法这个健康检查有什么问题吗?我提供了我最小的不工作的例子,以便任何人都可以测试它。我需要这个检查,以便能够启动另一个服务,它需要连接到注册表,只有当它准备好接受连接而不是在容器启动后,否则应用程序将失败并停止,除非我设置restart: on-failure
,但我宁愿只在其他服务启动时启动它,而不是继续重新启动希望找到注册表就绪。
这里的问题是容器的Jar
上没有filesystem
文件。为了使其可用,我们需要以下列方式使用卷:
jhipster-registry:
extends:
file: jhipster-registry.yml
service: jhipster-registry
mem_limit: 512m
ports:
- 8761:8761
networks:
- backend
volumes:
- ${PWD}/Ping.jar:/Ping.jar
healthcheck:
test: ["CMD", "java", "-jar", "/Ping.jar", "localhost", "8761"]
interval: 30s
retries: 20
并从根目录(Jar
)开始引用/
文件。