docker compose logging is not working with syslog option












1















I have a docker-compose configuration like this:



version: '3'
services:
worker:
image: // image
logging:
driver: syslog
options:
syslog-address: "udp://XXX.papertrailapp.com:XXXX"
tag: "{{.Name}}/{{.ID}}"


When I deploy this to digital ocean & ubuntu I can successfully run the docker-compose up command like so:



docker-compose -f docker-compose.yml up


When that command runs I can see this output



worker_2_844fc7675414 | WARNING: no logs are available with the 'syslog' log driver
worker_1_5c91a3426046 | WARNING: no logs are available with the 'syslog' log driver


It appears that 'syslog' is correctly configured for the docker-compose to run, but that perhaps the 'syslog' driver is not available?



All the instructions I can find for using syslog with docker refer to docker run commands, but how can I get syslog working with docker-compose?










share|improve this question


















  • 1





    I believe that message is simply telling you that you won't see any logs on your console because you have elected to send them to syslog instead. Have you actually checked to see if your logs are being successfully received at papertrail?

    – larsks
    Nov 22 '18 at 4:32













  • Since docker compose up is running in foreground, it will look for STDOUT logs of containers. You have changed the logging driver to syslog which means all the STDOUT of container will be sent to syslog. Use docker-compose -f docker-compose.yml up -d and look for logs in syslog.

    – Cyclops
    Nov 22 '18 at 12:23













  • @larsks I did check papertrail! Unfortunately not seeing the logs there :(...

    – dylanjha
    Nov 25 '18 at 3:44











  • @larsks, I had the papertrail details misconfigured! This is actually logging to papertrail, thank you!

    – dylanjha
    Nov 25 '18 at 9:57


















1















I have a docker-compose configuration like this:



version: '3'
services:
worker:
image: // image
logging:
driver: syslog
options:
syslog-address: "udp://XXX.papertrailapp.com:XXXX"
tag: "{{.Name}}/{{.ID}}"


When I deploy this to digital ocean & ubuntu I can successfully run the docker-compose up command like so:



docker-compose -f docker-compose.yml up


When that command runs I can see this output



worker_2_844fc7675414 | WARNING: no logs are available with the 'syslog' log driver
worker_1_5c91a3426046 | WARNING: no logs are available with the 'syslog' log driver


It appears that 'syslog' is correctly configured for the docker-compose to run, but that perhaps the 'syslog' driver is not available?



All the instructions I can find for using syslog with docker refer to docker run commands, but how can I get syslog working with docker-compose?










share|improve this question


















  • 1





    I believe that message is simply telling you that you won't see any logs on your console because you have elected to send them to syslog instead. Have you actually checked to see if your logs are being successfully received at papertrail?

    – larsks
    Nov 22 '18 at 4:32













  • Since docker compose up is running in foreground, it will look for STDOUT logs of containers. You have changed the logging driver to syslog which means all the STDOUT of container will be sent to syslog. Use docker-compose -f docker-compose.yml up -d and look for logs in syslog.

    – Cyclops
    Nov 22 '18 at 12:23













  • @larsks I did check papertrail! Unfortunately not seeing the logs there :(...

    – dylanjha
    Nov 25 '18 at 3:44











  • @larsks, I had the papertrail details misconfigured! This is actually logging to papertrail, thank you!

    – dylanjha
    Nov 25 '18 at 9:57
















1












1








1








I have a docker-compose configuration like this:



version: '3'
services:
worker:
image: // image
logging:
driver: syslog
options:
syslog-address: "udp://XXX.papertrailapp.com:XXXX"
tag: "{{.Name}}/{{.ID}}"


When I deploy this to digital ocean & ubuntu I can successfully run the docker-compose up command like so:



docker-compose -f docker-compose.yml up


When that command runs I can see this output



worker_2_844fc7675414 | WARNING: no logs are available with the 'syslog' log driver
worker_1_5c91a3426046 | WARNING: no logs are available with the 'syslog' log driver


It appears that 'syslog' is correctly configured for the docker-compose to run, but that perhaps the 'syslog' driver is not available?



All the instructions I can find for using syslog with docker refer to docker run commands, but how can I get syslog working with docker-compose?










share|improve this question














I have a docker-compose configuration like this:



version: '3'
services:
worker:
image: // image
logging:
driver: syslog
options:
syslog-address: "udp://XXX.papertrailapp.com:XXXX"
tag: "{{.Name}}/{{.ID}}"


When I deploy this to digital ocean & ubuntu I can successfully run the docker-compose up command like so:



docker-compose -f docker-compose.yml up


When that command runs I can see this output



worker_2_844fc7675414 | WARNING: no logs are available with the 'syslog' log driver
worker_1_5c91a3426046 | WARNING: no logs are available with the 'syslog' log driver


It appears that 'syslog' is correctly configured for the docker-compose to run, but that perhaps the 'syslog' driver is not available?



All the instructions I can find for using syslog with docker refer to docker run commands, but how can I get syslog working with docker-compose?







docker logging docker-compose syslog papertrail-app






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 1:47









dylanjhadylanjha

85111532




85111532








  • 1





    I believe that message is simply telling you that you won't see any logs on your console because you have elected to send them to syslog instead. Have you actually checked to see if your logs are being successfully received at papertrail?

    – larsks
    Nov 22 '18 at 4:32













  • Since docker compose up is running in foreground, it will look for STDOUT logs of containers. You have changed the logging driver to syslog which means all the STDOUT of container will be sent to syslog. Use docker-compose -f docker-compose.yml up -d and look for logs in syslog.

    – Cyclops
    Nov 22 '18 at 12:23













  • @larsks I did check papertrail! Unfortunately not seeing the logs there :(...

    – dylanjha
    Nov 25 '18 at 3:44











  • @larsks, I had the papertrail details misconfigured! This is actually logging to papertrail, thank you!

    – dylanjha
    Nov 25 '18 at 9:57
















  • 1





    I believe that message is simply telling you that you won't see any logs on your console because you have elected to send them to syslog instead. Have you actually checked to see if your logs are being successfully received at papertrail?

    – larsks
    Nov 22 '18 at 4:32













  • Since docker compose up is running in foreground, it will look for STDOUT logs of containers. You have changed the logging driver to syslog which means all the STDOUT of container will be sent to syslog. Use docker-compose -f docker-compose.yml up -d and look for logs in syslog.

    – Cyclops
    Nov 22 '18 at 12:23













  • @larsks I did check papertrail! Unfortunately not seeing the logs there :(...

    – dylanjha
    Nov 25 '18 at 3:44











  • @larsks, I had the papertrail details misconfigured! This is actually logging to papertrail, thank you!

    – dylanjha
    Nov 25 '18 at 9:57










1




1





I believe that message is simply telling you that you won't see any logs on your console because you have elected to send them to syslog instead. Have you actually checked to see if your logs are being successfully received at papertrail?

– larsks
Nov 22 '18 at 4:32







I believe that message is simply telling you that you won't see any logs on your console because you have elected to send them to syslog instead. Have you actually checked to see if your logs are being successfully received at papertrail?

– larsks
Nov 22 '18 at 4:32















Since docker compose up is running in foreground, it will look for STDOUT logs of containers. You have changed the logging driver to syslog which means all the STDOUT of container will be sent to syslog. Use docker-compose -f docker-compose.yml up -d and look for logs in syslog.

– Cyclops
Nov 22 '18 at 12:23







Since docker compose up is running in foreground, it will look for STDOUT logs of containers. You have changed the logging driver to syslog which means all the STDOUT of container will be sent to syslog. Use docker-compose -f docker-compose.yml up -d and look for logs in syslog.

– Cyclops
Nov 22 '18 at 12:23















@larsks I did check papertrail! Unfortunately not seeing the logs there :(...

– dylanjha
Nov 25 '18 at 3:44





@larsks I did check papertrail! Unfortunately not seeing the logs there :(...

– dylanjha
Nov 25 '18 at 3:44













@larsks, I had the papertrail details misconfigured! This is actually logging to papertrail, thank you!

– dylanjha
Nov 25 '18 at 9:57







@larsks, I had the papertrail details misconfigured! This is actually logging to papertrail, thank you!

– dylanjha
Nov 25 '18 at 9:57














1 Answer
1






active

oldest

votes


















0














This does in fact work. I erroneously had the papertrail details misconfigured so I was not seeing the logs.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422818%2fdocker-compose-logging-is-not-working-with-syslog-option%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    This does in fact work. I erroneously had the papertrail details misconfigured so I was not seeing the logs.






    share|improve this answer




























      0














      This does in fact work. I erroneously had the papertrail details misconfigured so I was not seeing the logs.






      share|improve this answer


























        0












        0








        0







        This does in fact work. I erroneously had the papertrail details misconfigured so I was not seeing the logs.






        share|improve this answer













        This does in fact work. I erroneously had the papertrail details misconfigured so I was not seeing the logs.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 25 '18 at 9:57









        dylanjhadylanjha

        85111532




        85111532
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422818%2fdocker-compose-logging-is-not-working-with-syslog-option%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            MongoDB - Not Authorized To Execute Command

            How to fix TextFormField cause rebuild widget in Flutter

            in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith