I am user docker-compse.yml. I found that it is running in docker . Here is the image:
But when I am going to run http://localhost:15672/, it is not connect to rabbitmq to browser. Here is my docker-compse.yml . But when i run the url http://localhost:5672/ , it shows only AMQP��
rabbitmq:
image: rabbitmq:3.8
mem_limit: 300m
ports:
- "5672:5672"
- "15672:15672"
volumes:
- 'rabbitmq_data:/bitnami'
networks:
- account-network
depends_on:
- service-registry
environment:
EUREKA.CLIENT.SERVICEURL.DEFAULTZONE: http://service-registry:8761/eureka
SPRING.ZIPKIN.BASEURL: http://zipkin-server:9411/
volumes:
rabbitmq_data:
driver: local
What is the problem ? Please help me.
You have to select a RabbitMQ image, which has the management plugin included. Like this:
rabbitmq:
image: rabbitmq:3-management-alpine
See here.
Related
please see below my docker-compose.yml and attached screenshot for hub logs. I am not seeing nodes getting attached to hub, any suggestions how to make it work.
Added screenshots for output of docker-compose.yml and containers created in Docker. When I am trying to launch localhost:4444, i am seeing err - The Grid has no registered Nodes yet
version: "3"
services:
hub:
image: selenium/hub
ports:
- "4444:4444"
chrome:
image: selenium/node-chrome
container_name: web-automation_chrome
depends_on:
- hub
volumes:
- /dev/shm:/dev/shm
ports:
- "9001:5900"
links:
- hub
firefox:
image: selenium/node-firefox
container_name: web-automation_firefox
depends_on:
- hub
volumes:
- /dev/shm:/dev/shm
ports:
- "9002:5900"
links:
- hub```
[![DockerContainerCreatedSuccessfully][1]][1]
[1]: https://i.stack.imgur.com/IiMpK.png
Note: Thanks #Ferran Buireu for the suggestion. I'm quite sure to get minus vote because of very new to docker and changing network world to system and programming.
After deploy gatsbyjs, I found the socketio error "net::ERR_CONNECTION_REFUSED".
Even it works properly when I browse to any pages but I think it is not running correctly.
How can I solve this error? (below is the error capture)
I implement and deploy these services on Ubuntu 20.04.2 with Docker 20.10.6, please see the below "docker-compose.yml"
version: "3"
services:
frontendapp01:
working_dir: /frontendapp01
build:
context: ./frontendapp01
dockerfile: Dockerfile
depends_on:
- backendsrv01
- mongoserver
volumes:
- ./sentric01:/srv/front
ports:
- "8001:8000"
environment:
GATSBY_WEBPACK_PUBLICPATH: /
STRAPI_URL: backendsrv01:1337
networks:
- vpsnetwork
frontendapp02:
working_dir: /frontendapp02
build:
context: ./frontendapp02
dockerfile: Dockerfile
depends_on:
- backendsrv02
- mongoserver
volumes:
- ./sentric02:/srv/front
ports:
- "8002:8000"
environment:
GATSBY_WEBPACK_PUBLICPATH: /
STRAPI_URL: backendsrv02:1338
networks:
- vpsnetwork
frontendapp03:
working_dir: /frontendapp03
build:
context: ./frontendapp03
dockerfile: Dockerfile
depends_on:
- backendsrv02
- mongoserver
volumes:
- ./sentric03:/srv/front
ports:
- "8003:8000"
environment:
GATSBY_WEBPACK_PUBLICPATH: /
STRAPI_URL: backendsrv02:1338
networks:
- vpsnetwork
backendsrv01:
image: strapi/strapi
container_name: backendsrv01
restart: unless-stopped
environment:
DATABASE_CLIENT: mongo
DATABASE_NAME: essential
DATABASE_HOST: mongoserver
DATABASE_PORT: 27017
networks:
- vpsnetwork
volumes:
- ./app01:/srv/app
ports:
- "1337:1337"
backendsrv02:
image: strapi/strapi
container_name: backendsrv02
restart: unless-stopped
environment:
DATABASE_CLIENT: mongo
DATABASE_NAME: solven
DATABASE_HOST: mongoserver
DATABASE_PORT: 27017
networks:
- vpsnetwork
volumes:
- ./app02:/srv/app
ports:
- "1338:1337"
mongoserver:
image: mongo
container_name: mongoserver
restart: unless-stopped
networks:
- vpsnetwork
volumes:
- vpsappdata:/data/db
ports:
- "27017:27017"
networks:
vpsnetwork:
driver: bridge
volumes:
vpsappdata:
The socket connection only appears during the development stage (gatsby develop) and it's intended to refresh and update the browser on each saves by hot-reloading, so without losing component state. This feature is known as fast-refresh.
As I said, and for obvious reasons, this only applies in gatsby develop. Under gatsby build, there's no connection socket. If your Docker development environment is sharing the port 8000 and 8001 (according to your docker-compose.yml setup), once built, can cause a break of the socket because it has changed the scope of the project.
Answering, you don't have to worry about, your project seems to build properly but, because of the sharing port between environments it prompts the log.
Further readings:
https://www.gatsbyjs.com/docs/conceptual/overview-of-the-gatsby-build-process/
https://www.gatsbyjs.com/docs/reference/local-development/fast-refresh/
I’ve spent an awful long time trying to debug this. I have an already populated docker compose file with multiple containers running, all on the same network. The containers consist of a tomcat9 server(Server A), a hazelcast container, and a hazelcast-mancenter container, and then an apache server.
I want to introduce an additional container, which is a tomcat7 server(Server B), and for some reason it interferes with the original tomcat server(Server A). Server A never gets to a start up state when server B's container is running.
Whenever Server B is off, Server A works no problem(after a restart). The moment Server B comes on, Server A poops out.
For some reason Server B also attempts to connect to Hazelcast or affects it. Even if I take Server B off the network as the other containers, there is still interference. I am certain that Server B is not attempting to connect to the original Hazelcast container.
What is going on? Shouldn’t the container be isolated?
docker-compose.yml
version: '3.7'
services:
server_a_tomcat:
container_name: server_a_tomcat
image: server_a:latest
ports:
- "8080:8080"
- "5005:5005"
networks:
- network_a
depends_on:
- server_a_mountebank_local
volumes:
- …/java-config
- …/server_a_tomcat.war
- data-volume:/usr/local/ssl
environment:
- …
server_a_mountebank_local:
container_name: server_a_mountebank_local
image: mountebank:latest
volumes:
- …
networks:
- network_a
ports:
- "8083:8083"
apache_local:
container_name: apache_local
image: apache_local:latest
ports:
- "80:80"
- "8055:8055"
depends_on:
- server_a_local
volumes:
- …/httpd.conf
- …/extra-httpd.conf
- …
- data-volume:/usr/local/ssl
networks:
- network_a
stdin_open: true
tty: true
hazelcast_local:
container_name: hazelcast_local
image: hazelcast_local:latest
ports:
- 11415:5701
depends_on:
- mancenter_local
mancenter_local:
container_name: mancenter_local
image: mancenter_local:latest
environment:
- HAZELCAST_IP={{ container_private_ip }}
- JAVA_OPTS=-Dhazelcast.mc.rest.enabled=true
ports:
- 8100:8080
networks:
- network_a
server_b_tomcat:
container_name: server_b_tomcat
build:
context: '.'
dockerfile: 'Dockerfile-server_b_tomcat’
ports:
- "9090:8080"
- "5015:5005"
environment:
- ...
networks:
- network_b
depends_on:
- redis
redis:
container_name: redis
image: redis:5.0.5
ports:
- "6379:6379"
networks:
- network_b
networks:
network_b:
driver: bridge
name: network_b
network_a:
driver: bridge
name: network_a
volumes:
data-volume:
I am currently working on a mobile app that connects to a server instance in docker through a docker-compse instance that can be see by an emulator on my developemnt machine fine, but if I try and use my mobile I can't see the server as it is not on the same network. is there easy way I can set this up to so it can be seen by both my emulator and my mobile at the same time.
my Docker composer setup is
version: '3.1'
services:
node:
container_name: nodejs
build: .
#restart: always
ports:
- 8080:8080
- 3000:3000
volumes:
- .:/usr/src/app
environment:
PORT: 3000
extra_hosts:
- "nodeserver:10.1.1.222"
depends_on:
- mongo
mongo:
container_name: mongodb
image: mongo
restart: always
ports:
- 27017:27017
volumes:
- ./db:/data/db
command: mongod
mongo-express:
container_name: mongoExpress
image: mongo-express
restart: always
ports:
- 9081:8081
environment:
ME_CONFIG_MONGODB_USERNAME: admin
ME_CONFIG_MONGODB_PASSWORD: password
depends_on:
- mongo
I am not a big net-ops guy some so any real help here would appreciated.
I would like to have my customized image based on rabbitmq. That customized image I like to create with docker-compose. I want management plugi started
If I use docker compose as
rabbitmq: # https://registry.hub.docker.com/_/rabbitmq/
image: rabbitmq:3-management
ports:
- 5672:5672
- 15672:15672
- 8080:8080
it does bring up management plugin.
If I use docker compose
version: '2'
services:
# Rabbit service. See https://hub.docker.com/_/rabbitmq/
rabbit:
container_name: dev-rabbit
image: rabbitmq-our:3-management
build: ./rabbitmq-our
environment:
- RABBITMQ_DEFAULT_USER=rabbit
- RABBITMQ_DEFAULT_PASS=mq
- RABBITMQ_DEFAULT_VHOST=my_vhost
ports:
- "4369:4369"
- "5671:5671"
- "5672:5672"
- "15672:15672"
- "8080:8080"
and Dockerfile in rabbitmq-our/ folder such as
FROM rabbitmq
Then no plugins are started and I am not getting the management console.
How I can specify running that "3-management" plugin in my custom image startup ?
I've my compose like this and works the RabbitMQ admin plugin.
rabbit:
container_name: dev_rabbit
hostname: rabbit
image: rabbitmq:3.6.6-management
environment:
- RABBITMQ_DEFAULT_USER=user
- RABBITMQ_DEFAULT_PASS=user
ports:
- "5672:5672"
- "15672:15672"
I take it from the hub.docker official page.