if loki is not reachable and loki-docker-driver is activated, containers apps stops and cannot be stopped/killed
**Describe the bug** we have installed the loki-docker-driver on all our devices. The loki server on an extra server, if the loki-server is updated/restarted or just not reachable then after a short time all containers get stuck (docker logs does not update anymore). If the loki-server is not reachable, the containers can neither be stopped/kill nor restarted. **To Reproduce** Steps to reproduce the behavior: 1. start loki server (server) 2. install loki-docker-driver on another system (can also be tested on one and the same system) (client) 2.1. ```/etc/docker/daemon.json``` ``` { "live-restore": true, "log-driver": "loki", "log-opts": { "loki-url": "http://loki:3100/api/prom/push", "mode": "non-blocking", "loki-batch-size": "400", "max-size": "1g" } } ``` 3. ```docker run --rm --name der-container -d debian /bin/sh -c "while true; do date >> /tmp/ts ; seq 0 1000000; sleep 1 ; done"```(client) 4. ```docker exec -it der-container tail -f /tmp/ts``` shows every second the time (client) 5. ```docker logs -f der-container``` show numbers from 0-1000000 (client) 6. stop loki server (server) 7. you will see that the outputs on the system stop with the loci-driver and that you cannot stop the container (client) 8. ``` docker stop der-container ``` (client) **Expected behavior** A clear and concise description of what you expected to happen. I would like all containers to continue to run as desired even if the loci is
Posted by badsmoke on Jul 16, 2020, 1:37 PM
Tags
Related issues
- CC v2.1.100+ inflates cache_creation by ~20K tokens vs v2.1.98 — same payload, server-side
- Max Plan: Token usage increased ~3-5x without any configuration change (since ~March 28-29)
- I use 43" Dell Ultrasharp, it comes with built-in kvm for switching between signal sources so I can connect both my macbook and linux lap...
- Feature Request: Official Headless Mode & Enhanced CLI for Steam Client
- Linux workspace rendering issues
- Git - create git graph visualization
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
onboarding (Sysadmin)
CC v2.1.100+ inflates cache_creation by ~20K tokens vs v2.1.98 — same payload, server-side
Max Plan: Token usage increased ~3-5x without any configuration change (since ~March 28-29)
I use 43" Dell Ultrasharp, it comes with built-in kvm for switching between signal sources so I can connect both my macbook and linux lap...
Feature Request: Official Headless Mode & Enhanced CLI for Steam Client
Linux workspace rendering issues
Git - create git graph visualization
High memory usage from VMMEM with docker desktop windows x64 V4.12.0
Cannot apply CRD and a CR using it in the same plan/apply due to SSA
if loki is not reachable and loki-docker-driver is activated, containers apps stops and cannot be stopped/killed
**Describe the bug** we have installed the loki-docker-driver on all our devices. The loki server on an extra server, if the loki-server is updated/restarted or just not reachable then after a short time all containers get stuck (docker logs does not update anymore). If the loki-server is not reachable, the containers can neither be stopped/kill nor restarted. **To Reproduce** Steps to reproduce the behavior: 1. start loki server (server) 2. install loki-docker-driver on another system (can also be tested on one and the same system) (client) 2.1. ```/etc/docker/daemon.json``` ``` { "live-restore": true, "log-driver": "loki", "log-opts": { "loki-url": "http://loki:3100/api/prom/push", "mode": "non-blocking", "loki-batch-size": "400", "max-size": "1g" } } ``` 3. ```docker run --rm --name der-container -d debian /bin/sh -c "while true; do date >> /tmp/ts ; seq 0 1000000; sleep 1 ; done"```(client) 4. ```docker exec -it der-container tail -f /tmp/ts``` shows every second the time (client) 5. ```docker logs -f der-container``` show numbers from 0-1000000 (client) 6. stop loki server (server) 7. you will see that the outputs on the system stop with the loci-driver and that you cannot stop the container (client) 8. ``` docker stop der-container ``` (client) **Expected behavior** A clear and concise description of what you expected to happen. I would like all containers to continue to run as desired even if the loci is
Comments (0)
No comments yet. Start the discussion.