#docker

/

      • doodoo joined the channel
      • iAmerikan joined the channel
      • leedm777 has quit
      • StuartW joined the channel
      • NET||abuse has quit
      • jancoow has quit
      • zerocoolback joined the channel
      • e14 joined the channel
      • enderandpeter joined the channel
      • zerocoolback has quit
      • ash_work joined the channel
      • e14 joined the channel
      • ash_work
        without customizing an image or keeping the log locally, is there a way to give /var/log/.../error.log write permissions to a user
      • thegattaca has quit
      • larsks
        ash_work: not that I can think of. All the solutions that come to mind quickly would require at least running chown/chmod or something similar.
      • ash_work
        larsks: I guess I should want errors to be reported to docker
      • larsks
        Do you mean...make error.log available to a user *inside* the container? Or something else?
      • ash_work
        like how it might show if you do `docker-compose up`
      • larsks: well, was thinking I wanted to be able to just `docker exec <container> tail -f /var/log/php/error.php`
      • larsks
        That should work just fine.
      • My first answer was due to bad assumptions and doesn't apply.
      • Spanktar has quit
      • ash_work
        larsks: no because www-data doesn't have write perms on that dir
      • larsks: so your answer *does* apply
      • larsks
        You mean, read perms? Because you don't need write just to tail...
      • I guess there is a "USER www-data" directive in your dockerfile?
      • ash_work
        larsks: I wont have anything to tail
      • larsks: in the default, yes
      • larsks
        Ah, I see. You mean you can't write the error log there in the first place?
      • milardovich has quit
      • ash_work
        larsks: not without building my own image... which I find a bit silly *just* for a mkdir statement
      • larsks
        I don't think it's silly. I mean, that's what Dockerfiles are for: applying changes to an existing image to get what you want. It's nice when they're small and easy to understand :)
      • ash_work
        larsks: but just now I was thinking of abandoning that idea and have it reported to docker (the way errors might naturally show up if you ran `docker-compose up` in the foreground)
      • larsks: I think I might need to do that anyway for integration with an IDE, right?
      • larsks
        That's also a great idea, if you can modify the image so that your service is logging to stdout/stderr.
      • ash_work
        larsks: yeah, it does so by default, but I didn't know if that was better or worse
      • larsks
        I would argue it's generally better, since seeing the logs in that case doesn't require access inside the container.
      • Plus it means you have a single place to look at logs, instead of poking about a multitude of containers.
      • I have to run off. Good luck!
      • ziyourenxiang joined the channel
      • milardovich joined the channel
      • jbrooks joined the channel
      • OpenSorceress joined the channel
      • ash_work
        larsks: thank you!
      • :)
      • Lenz has quit
      • iAmerikan joined the channel
      • e14 has quit
      • doodoo joined the channel
      • jbrooks joined the channel
      • dreamcat4 joined the channel
      • enderandpeter1 joined the channel
      • enderandpeter has quit
      • enderandpeter1 is now known as enderandpeter
      • blacknred0 has quit
      • JasonCL has quit
      • coumbole has quit
      • aidalgol has quit
      • aidalgol joined the channel
      • Lenz joined the channel
      • trevor joined the channel
      • aossama has quit
      • e14 joined the channel
      • awkwardpenguin joined the channel
      • onmeac has quit
      • GenteelBen has quit
      • StuartW has quit
      • AfroThundr joined the channel
      • Lenz has quit
      • JasonCL joined the channel
      • minionofgozer joined the channel
      • nlogex has quit
      • nlogex joined the channel
      • aossama joined the channel
      • minionofgozer joined the channel
      • StuartW joined the channel
      • tw2113 joined the channel
      • aossama has quit
      • pmercado_ joined the channel
      • LennardW|afk joined the channel
      • pmercado has quit
      • tw2113 has left the channel
      • matt8109 joined the channel
      • aossama joined the channel
      • matt8109 has quit
      • vendull joined the channel
      • pt1 joined the channel
      • minionofgozer joined the channel
      • aossama has quit
      • pt1 has quit
      • nlogex has quit
      • brainpro1 joined the channel
      • JasonCL has quit
      • obiwan90 joined the channel
      • JasonCL joined the channel
      • goatish has quit
      • smccarthy joined the channel
      • matt8109 joined the channel
      • brainproxy has quit
      • Arcaelyx joined the channel
      • aossama joined the channel
      • lessless joined the channel
      • JasonCL has quit
      • aossama has quit
      • groundup joined the channel
      • keldwud has quit
      • groundup
        The issue of logging application logs has been on my mind since before DockerCon and was the main reason I went. I learned a lot of companies are doing it but I didn't find much in the ways of best practices for an open source alternative.
      • StuartW has quit
      • Every tutorial takes the easy route of logging Nginx access logs. I want to know how best to log my multi-line PHP exception logs and the logs my PHP application generates.
      • linex joined the channel
      • toxync02 has quit
      • I really like having them go to stdout because then my container doesn't have to be aware of what's consuming those logs. However, we all know multi-line logs don't work with Docker logs. So, what's the solution there?
      • quesker joined the channel
      • zerocoolback joined the channel
      • linex
        All this while I have been testing docker on a physical host. Is there anything different I should know if I test it on a virtual machine, besides the performance obviously ?
      • fc5dc9d4_ joined the channel
      • aossama joined the channel
      • groundup
        linex: if your VM has access to it (network, peripherals, etc) then it should be the same
      • zerocoolback has quit
      • fc5dc9d4 has quit
      • hygl has quit
      • justAllgood has quit
      • linex
        groundup: yes, bridged
      • pmercado_ has quit
      • groundup
        You _should_ be good, but just test it :)
      • linex
        ok thanks
      • doodoo joined the channel
      • Bryson has quit
      • evansbee joined the channel
      • enderandpeter has quit
      • tm joined the channel
      • e14 joined the channel
      • aielima has quit
      • pmercado_ joined the channel
      • StuartW joined the channel
      • aielima joined the channel
      • daMaestro joined the channel
      • doodoo has quit
      • JasonCL joined the channel
      • JasonCL has quit
      • JasonCL joined the channel
      • aossama has quit
      • JasonCL has quit
      • JasonCL joined the channel
      • JasonCL has quit
      • trapier_ joined the channel
      • pmercado_ has quit
      • LennardW|afk joined the channel
      • zerocoolback joined the channel
      • aossama joined the channel