Error grabbing logs unexpected eof - Исправление ошибок и поиск оптимальных решений проблем

Description
Seem to be having issues tailing logs after upgrading to 17.09.0-ce. Was working on 17.06.0-ce

Steps to reproduce the issue:

Create container
Start container
Tail logs

Describe the results you received:

20:34:13 Error grabbing logs: EOF
20:34:13 [localhost] local: git checkout ./.dockerignore
20:34:13 Traceback (most recent call last):
20:34:13   File "$PATH@2/venv/local/lib/python2.7/site-packages/fabric/main.py", line 743, in main
20:34:13     *args, **kwargs
20:34:13   File "$PATH@2/venv/local/lib/python2.7/site-packages/fabric/tasks.py", line 424, in execute
20:34:13     results['<local-only>'] = task.run(*args, **new_kwargs)
20:34:13   File "$PATH@2/venv/local/lib/python2.7/site-packages/fabric/tasks.py", line 174, in run
20:34:13     return self.wrapped(*args, **kwargs)
20:34:13   File "$PATH@2/fabfile/__init__.py", line 142, in run_e2e_tests
20:34:13     e2e_tests.run(specs)
20:34:13   File "$PATH@2/fabfile/e2e_tests.py", line 69, in run
20:34:13     docker_build.copy_from(build_tag, '/blend/e2e/artifacts/.', 'artifacts')
20:34:13   File "$PATH@2/fabfile/docker_build.py", line 240, in copy_from
20:34:13     with tarfile.open(mode='r|*', fileobj=container.get_archive(source)[0]) as tarball:
20:34:13   File "$PATH@2/venv/local/lib/python2.7/site-packages/docker/models/containers.py", line 194, in get_archive
20:34:13     return self.client.api.get_archive(self.id, path)
20:34:13   File "$PATH@2/venv/local/lib/python2.7/site-packages/docker/utils/decorators.py", line 19, in wrapped
20:34:13     return f(self, resource_id, *args, **kwargs)
20:34:13   File "$PATH@2/venv/local/lib/python2.7/site-packages/docker/utils/decorators.py", line 34, in wrapper
20:34:13     return f(self, *args, **kwargs)
20:34:13   File "/mnt/jenkins-slave/workspace/blend-test-e2e-multitenant@2/venv/local/lib/python2.7/site-packages/docker/api/container.py", line 732, in get_archive
20:34:13     self._raise_for_status(res)
20:34:13   File "$PATH@2/venv/local/lib/python2.7/site-packages/docker/api/client.py", line 222, in _raise_for_status
20:34:13     raise create_api_error_from_http_exception(e)
20:34:13   File "$PATH@2/venv/local/lib/python2.7/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
20:34:13     raise cls(e, response=response, explanation=explanation)

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

Client:
 Version:      17.09.0-ce
 API version:  1.32
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:42:18 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.09.0-ce
 API version:  1.32 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:40:56 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:

Containers: 19
 Running: 7
 Paused: 0
 Stopped: 12
Images: 40
Server Version: 17.09.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 06b9cb35161009dcb7123345749fef02f7cea8e0
runc version: 3f2f8b84a77f73d38244dd690525642a72156c64
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: REDACT
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 14.69GiB
Name: REDACT
ID: 4NVG:MGS6:QUMP:GA7Z:5CPC:UVA2:AA2Q:XIL4:PSCM:QMX4:SULJ:Y4XQ
Docker Root Dir: REDACT
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 118
 Goroutines: 131
 System Time: 2017-11-01T21:28:08.293959958Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):

Executed using docker-py python library.

container.logs(
        follow=True,
        stdout=True,
        stderr=True,
        stream=True,
        tail=2
    )

Источник

Docker can’t read logs #1984

Comments

Expected behavior

Be able to read docker logs, despite any error messages. docker events command should work or display some human-readable error

Actual behavior

When docker container is not stopped gracefully (ie computer is shut down while containers running), logs become corrupt and can no longer be read. Error message:

The command docker events will run forever without exiting or outputting anything.

My workaround so far has been to use «Remove all data» feature under «Reset» in preferences, but its frustrating to reinstall all containers whenever I forget to stop containers or computer auto-updates.

Information

Docker for Mac: version: 17.06.0-ce-mac19 (4cdec4294a50b2233146b09469b49937dabdebdd)
macOS: version 10.12.6 (build: 16G29)
logs: /tmp/A2C0DE10-7188-4A98-93D8-9EAD1A849527/20170822-104841.tar.gz
[OK] db.git
[OK] vmnetd
[OK] dns
[OK] driver.amd64-linux
[OK] virtualization VT-X
[OK] app
[OK] moby
[OK] system
[OK] moby-syslog
[OK] db
[OK] env
[OK] virtualization kern.hv_support
[OK] slirp
[OK] osxfs
[OK] moby-console
[OK] logs
[OK] docker-cli
[OK] menubar
[OK] disk

Steps to reproduce the behavior

run containers
shut down computer (w/o stopping them)
start up and run containers
attempt to access logs

The text was updated successfully, but these errors were encountered:

Источник

Error grabbing logs: unexpected EOF #913

I am currently using WatchTower to watch a container with a NodeJS application. The container works fine, however when it is restarted by WatchTower, after a little moment (and a few logs), an error occurs:
Error grabbing logs: unexpected EOF

The container stills works fine except for the logs which are not showing up in the console any more.
When I restart the container manually without using WatchTower, there is no log issue. Is there some flags I should use in the docker-compose file in order to make it work ?

Thank you in advance,
B.