I’m sorry but I only have limited experience with docker. Before that I was able to run things smoothly. The problem started after upgrading to macos 10.15.7. I run docker-compose up -d to create the app. entryPoints=Name:http Address::80 $PathPrefixStrip:/monitor" This can use let's encrypt to generate a SSL cert. Here is my docker-compose.yml file: version: '3.5' Here is the result of docker ps docker psĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĭ46319e43bd5 clowder/clowder:latest "/bin/sh -c /home/cl…" 3 hours ago Up 3 hours (unhealthy) 9000/tcp clowder_clowder_1Ī1c4a3240a4a clowder/monitor:latest "/bin/sh -c 'python …" 3 hours ago Up 3 hours 9999/tcp clowder_monitor_1įa4e9662b1c8 traefik:1.7 "/traefik -loglevel…" 3 hours ago Up 3 hours 0.0.0.0:8000->80/tcp, 0.0.0.0:8443->443/tcp clowder_traefik_1Ī59cf98c71c7 mongo:3.6 "docker-entrypoint.s…" 3 hours ago Up 3 hours 27017/tcp clowder_mongo_1ĥ496405f71e7 elasticsearch:2 "/docker-entrypoint.…" 3 hours ago Up 3 hours 9200/tcp, 9300/tcp clowder_elasticsearch_1ħc2c986527d8 rabbitmq:management-alpine "docker-entrypoint.s…" 3 hours ago Up 3 hours 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 15691-15692/tcp, 25672/tcp clowder_rabbitmq_1 This fact does not allow me to run the application on localhost. Specifically the unhealthy message I get for the Status of the clowder image. Now, that are a lot of images and elements to keep in sync just to provide a password manager solution. I’ve been struggling with an issue over the past few days. The official Bitwarden solution can also be self-hosted via Docker but it is a bit much to maintain coming in with a big stack of eleven (11) containers.
0 kommentar(er)
