I am using eureka container but unfortunately it is not working properly.
Docker-compose.yaml
configserver:
image: 1.2.3.4:1234/configserver
container_name: configserver
ports:
- 8888:8888
volumes:
- /tmp/logs:/tmp/logs
env_file:
- ./docker.env
eureka:
container_name: eureka
ports:
- 8761:8080
volumes:
- /tmp/logs:/tmp/logs
env_file:
- ./docker.env
image: netflixoss/eureka:1.3.1
restart: always
depends_on:
- configserver
Logs of Container-
WARN com.netflix.discovery.DiscoveryClient:1570 [localhost-startStop-1]
[makeRemoteCall] Can't get a response from localhost:8080/eureka/v2/apps
ERROR com.netflix.discovery.DiscoveryClient:1432 [localhost-startStop-1] [makeRemoteCall] Can't contact any eureka nodes - possibly a security group issue?
ERROR com.netflix.discovery.DiscoveryClient:1033 [localhost-startStop-1] [fetchRegistry] DiscoveryClient_EUREKA/4ae83dcdde1a - was unable to refresh its cache! status = java.net.SocketTimeoutException: Read timed out
I used different image. Instead of netflixoss/eureka:1.3.1 I use eureka. It works for me.
Related
I'm trying to start 3 containers (Grafana, Chronograf, and InfluxDB) on my Ubuntu server.
I always get this nothing saying error message with my InfluxDB container:
root#h2860848:/docker/pp# docker start pp_influxdb
Error response from daemon: driver failed programming external connectivity on endpoint pp_influxdb (9e09cff68d7106f06e2dbb02c73a200ed435ee243e25f0963296ef6ced3a5d54): Error starting userland proxy:
Error: failed to start containers: pp_influxdb
I use this docker-compose file:
version: "3.9"
services:
influxdb:
image: influxdb: latest
restart: always
container_name: pp_influxdb
ports:
- "4083:8083"
- "4086:8086"
- "4090:8090"
- "4003:2003"
env_file:
- 'env.influxdb'
volumes:
- /docker/pp/influxdb/data:/var/lib/influxdb
chronograf:
image: chronograf:latest
container_name: pp_chronograf
restart: always
ports:
- '8888:8888'
volumes:
- /docker/pp/chronograf/data:/var/lib/chronograf
depends_on:
- influxdb
env_file:
- 'env.chronograf'
grafana:
image: grafana/grafana:latest
restart: always
container_name: pp_grafana
ports:
- "3000:3000"
env_file:
- 'env.grafana'
volumes:
- /docker/pp/grafana/data:/var/lib/grafana
As you can see, I already tried to change the ports, but nothing changed. The other containers are running perfectly. So, what's the problem?
(I'm like a beginner to Docker/Linux/etc.). Trying to get Heimdall working, but getting the error:
deployment error failed to deploy a stack: root additional property Heimdall is not allowed
This is the stack I'm trying to deploy:
heimdall:
image: ghcr.io/linuxserver/heimdall
container_name: heimdall
environment:
- PUID=1000
- PGID=1000
- TZ=Netherlands/Amsterdam
volumes:
- /home/me/docker/heimdall/config:/config
ports:
- 11080:80
- 11443:443
restart: always
Also added the "docker" user to my username group.
Hope someone can give me some insight about this.
Kind regads.
I have 2 working containers for Hadoop HDFS (I have built a Dockerfile for them starting from the one here) and need to add a HIVE instance to the set.
I cannot find a good working image to use (it would be nice to have version 2.3.4).
Is there anything you suggest, easy to add, that I could use?
Thank you!
Edit:
Here is a try I did:
hive-server:
container_name: hive-server
image: bde2020/hive:2.3.2-postgresql-metastore
depends_on:
- hadoop-namenode
env_file:
- ./hive_build/hadoop-hive.env
environment:
HIVE_CORE_CONF_javax_jdo_option_ConnectionURL: "jdbc:postgresql://hive-metastore/metastore"
SERVICE_PRECONDITION: "hive-metastore:9083"
ports:
- "10000:10000"
restart: unless-stopped
hive-metastore:
container_name: hive-metastore
image: bde2020/hive:2.3.2-postgresql-metastore
depends_on:
- hive-server
- hive-metastore-postgresql
env_file:
- ./hive_build/hadoop-hive.env
command: /opt/hive/bin/hive --service metastore
environment:
SERVICE_PRECONDITION: "hadoop-namenode:50070 hadoop-datanode1:50075 hive-metastore-postgresql:5432"
ports:
- "9083:9083"
restart: unless-stopped
hive-metastore-postgresql:
container_name: hive-metastore-postgresql
image: bde2020/hive-metastore-postgresql:2.3.0
ports:
- "5433:5432"
restart: unless-stopped
but when I enter it and try to connect I get an error:
docker exec -it hive-server bash
/opt/hive/bin/beeline -u jdbc:hive2://localhost:10000
error:
19/05/03 09:13:46 [main]: WARN jdbc.HiveConnection: Failed to connect to localhost:10000
Could not open connection to the HS2 server. Please check the server URI and if the URI is correct, then ask the administrator to check the server status.
Error: Could not open client transport with JDBC Uri: jdbc:hive2://localhost:10000: java.net.ConnectException: Connection refused (Connection refused) (state=08S01,code=0)
i have a simple spring cloud project,and it contains 4 services:
config:8888
registry(eureka):8761
gateway(zuul):8080
service-1:9527
enter image description here
the project has no problem if deployed in localhost,
i can successfully fetch service-1's api by zuul without docker:
http://localhost:8080/service-1/test
but when i deployed with docker,
it throws error: Caused by: java.lang.RuntimeException: org.apache.http.conn.HttpHostConnectException: Connect to registry:9527 [registry/172.21.0.4] failed: Connection refused (Connection refused)
i can only fetch with service-1's api
http://localhost:9527/test
PS: the two services(gateway,service-1) has been success registry to eureka
here is my docker-compose yml :
version: '3'
services:
config:
build: ./config
ports:
- "8888:8888"
registry:
build: ./registry
ports:
- "8761:8761"
depends_on:
- config
environment:
- SPRING_PROFILES_ACTIVE=prd
gateway:
build: ./gateway
depends_on:
- config
links:
- registry
- service-1
ports:
- "8080:8080"
environment:
- SPRING_PROFILES_ACTIVE=prd
service-1:
build: ./service-1
ports:
- "9527:9527"
depends_on:
- config
links:
- registry
environment:
- SPRING_PROFILES_ACTIVE=prd
can anyone help me?
i have solved this issue , i forgot add #EnableDiscoveryClient on gateway main class,and cover the eureka instance hostname
Good Morning,
I'm currently unable to get any of the listeners working to display data in the Hygieia dashboard. Right now I'm just trying to get sonar results displayed. The sonar instance is up and running at localhost:9000 with scan results.
My compose file looks like the following:
mongodb:
image: mongo:latest
container_name: mongodb
command: mongod --smallfiles
ports:
- "27017:27017"
volumes:
- ./mongo:/var/lib/mongo/:rw
volume_driver: local
hygieia-api:
image: hygieia-api:latest
container_name: hygieia-api
ports:
- "8080:8080"
volumes:
- ./logs:/hygieia/logs
links:
- mongodb:mongo
hygieia-ui:
image: hygieia-ui:latest
container_name: hygieia-ui
ports:
- "8088:80"
links:
- hygieia-api
hygieia-sonar-codequality-collector:
image: hygieia-sonar-codequality-collector:latest
container_name: hygieia-sonar-codequality
volumes:
- ./logs:/hygieia/logs
links:
- mongodb:mongo
- hygieia-api
My override file:
hygieia-sonar-codequality-collector:
environment:
- SONAR_CRON=*/1 * * * *
- SONAR_URL=http://localhost:9000
- SONAR_API=http://localhost:9000/api/projects/index/
My application.properties file:
dbname=dashboard
dbhost=localhost
dbport=27017
dbusername=dashboarduser
dbpassword=dbpassword
sonar.cron=0 0/5 * * * *
sonar.servers[0]=http://localhost:9000
sonar.metrics=ncloc,line_coverage,violations,critical_violations,major_violations,blocker_violations,sqale_index,test_success_density,test_failrues,test_errors,tests
I've had the same issue with JIRA and Jenkins as well and have not been able to get any test results into the dashboard. Thank you for any help.
EDIT:
2017-03-08 17:34:32,007 ERROR c.c.d.collector.DefaultSonarClient - org.springframework.web.client.ResourceAccessException: I/O error on GET request for "http://0.0.0.0:9000/api/resources?format=json":Connect to 0.0.0.0:9000 [/0.0.0.0] failed: Connection refused (Connection refused); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to 0.0.0.0:9000 [/0.0.0.0] failed: Connection refused (Connection refused)
This seems to be my issue, however I am able to connect to the above url successfully..
Fixed my issue by pointing to the ip address of the container instead of localhost.