portainer: Portainer logs is unable to display the complete text of the logs

Attaching both actual logs and logs from portianer log viewer screen shot 2018-03-07 at 3 19 41 pm actual.txt

Started using Portainer 1.16.3 and can see the complete log text is not visible in the logs section. it is displaying alright when there is no stack trace. but as soon as there is an exception the initial text are missing.

Steps to reproduce the issue:

  1. Update portainer to 1.16.3
  2. run a java app and let it dump a stack trace (exception)
  3. view the logs from portainer logs section

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?

Technical details:

  • Portainer version: 1.16.3
  • Target Docker version (the host/cluster you manage):17.12.0-ce
  • Platform (windows/linux): linux
  • Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): stack deploy
  • Target Swarm version (if applicable):
  • Browser: chrome

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 1
  • Comments: 21 (8 by maintainers)

Commits related to this issue

Most upvoted comments

I am having the exact same problem, but it doesn’t matter if it’s a stack-trace or not, it happens to all of my containers that prints all kinds of stuff.

  • Portainer version: 1.16.4
  • Target Docker version (the host/cluster you manage):17.12.1-ce
  • Platform (windows/linux): linux
  • Command used to start Portainer: docker run -p 5704:9000 portainer/portainer
  • Browser: chrome

It seems to be tied to “Config”: { “Tty”: true If I duplicate and re-deploy after setting only interactive (-i) instead of (-i -t) the log doesn’t truncate, but I don’t see the output that I should (as I require an interactive session). I need to confirm, but I wasn’t seeing this a few weeks ago before I updated my docker runtime, now with on CE 18.03 it is affecting all containers in my template file where I set interactive: true

tty: true image

tty:false image

Hi Guys, Thanks for fixing this i see this working in new version

I can also confirm that the logs look right after loading portainer:pr1861 (even without restarting the suspect containers). Great!

it also works fine in my home environment. properly showing all logs, exceptions, etc…