docker-compose unkown host?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I can not use the AWS SDK putObject to upload a file to a fake s3 in local stack. I get an unknown host exception when I try to call putObject. The SDK is calling out to my-bucket.localstack:4572 but my docker contain does not seem to be able to resolve the request and throws a unknown host exception. Is there away to point my-bucket.localstack:4572 to localstack?



version: "3"
services:
app:
image: app:latest
command: run
networks:
- mynetwork
ports:
- 8000:8080
environment:
- AWS_ACCESS_KEY_ID=111
- AWS_SECRET_ACCESS_KEY=111
- AWS_REGION=us-east-1
- spring_profiles_active=local

localstack:
image: localstack/localstack
networks:
- mynetwork
ports:
- "4567-4584:4567-4584"
- "${PORT_WEB_UI-8080}:${PORT_WEB_UI-8080}"
environment:
- SERVICES=sqs,s3

networks:
mynetwork:
driver: bridge









share|improve this question





























    0















    I can not use the AWS SDK putObject to upload a file to a fake s3 in local stack. I get an unknown host exception when I try to call putObject. The SDK is calling out to my-bucket.localstack:4572 but my docker contain does not seem to be able to resolve the request and throws a unknown host exception. Is there away to point my-bucket.localstack:4572 to localstack?



    version: "3"
    services:
    app:
    image: app:latest
    command: run
    networks:
    - mynetwork
    ports:
    - 8000:8080
    environment:
    - AWS_ACCESS_KEY_ID=111
    - AWS_SECRET_ACCESS_KEY=111
    - AWS_REGION=us-east-1
    - spring_profiles_active=local

    localstack:
    image: localstack/localstack
    networks:
    - mynetwork
    ports:
    - "4567-4584:4567-4584"
    - "${PORT_WEB_UI-8080}:${PORT_WEB_UI-8080}"
    environment:
    - SERVICES=sqs,s3

    networks:
    mynetwork:
    driver: bridge









    share|improve this question

























      0












      0








      0


      0






      I can not use the AWS SDK putObject to upload a file to a fake s3 in local stack. I get an unknown host exception when I try to call putObject. The SDK is calling out to my-bucket.localstack:4572 but my docker contain does not seem to be able to resolve the request and throws a unknown host exception. Is there away to point my-bucket.localstack:4572 to localstack?



      version: "3"
      services:
      app:
      image: app:latest
      command: run
      networks:
      - mynetwork
      ports:
      - 8000:8080
      environment:
      - AWS_ACCESS_KEY_ID=111
      - AWS_SECRET_ACCESS_KEY=111
      - AWS_REGION=us-east-1
      - spring_profiles_active=local

      localstack:
      image: localstack/localstack
      networks:
      - mynetwork
      ports:
      - "4567-4584:4567-4584"
      - "${PORT_WEB_UI-8080}:${PORT_WEB_UI-8080}"
      environment:
      - SERVICES=sqs,s3

      networks:
      mynetwork:
      driver: bridge









      share|improve this question














      I can not use the AWS SDK putObject to upload a file to a fake s3 in local stack. I get an unknown host exception when I try to call putObject. The SDK is calling out to my-bucket.localstack:4572 but my docker contain does not seem to be able to resolve the request and throws a unknown host exception. Is there away to point my-bucket.localstack:4572 to localstack?



      version: "3"
      services:
      app:
      image: app:latest
      command: run
      networks:
      - mynetwork
      ports:
      - 8000:8080
      environment:
      - AWS_ACCESS_KEY_ID=111
      - AWS_SECRET_ACCESS_KEY=111
      - AWS_REGION=us-east-1
      - spring_profiles_active=local

      localstack:
      image: localstack/localstack
      networks:
      - mynetwork
      ports:
      - "4567-4584:4567-4584"
      - "${PORT_WEB_UI-8080}:${PORT_WEB_UI-8080}"
      environment:
      - SERVICES=sqs,s3

      networks:
      mynetwork:
      driver: bridge






      docker docker-compose






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 3 at 16:07









      Freid001Freid001

      732826




      732826
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Configuring the AWS SDK to use path style access resolved my problem.



          See this Github issue: https://github.com/localstack/localstack/issues/43#issuecomment-308273958






          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%2f54025920%2fdocker-compose-unkown-host%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














            Configuring the AWS SDK to use path style access resolved my problem.



            See this Github issue: https://github.com/localstack/localstack/issues/43#issuecomment-308273958






            share|improve this answer




























              0














              Configuring the AWS SDK to use path style access resolved my problem.



              See this Github issue: https://github.com/localstack/localstack/issues/43#issuecomment-308273958






              share|improve this answer


























                0












                0








                0







                Configuring the AWS SDK to use path style access resolved my problem.



                See this Github issue: https://github.com/localstack/localstack/issues/43#issuecomment-308273958






                share|improve this answer













                Configuring the AWS SDK to use path style access resolved my problem.



                See this Github issue: https://github.com/localstack/localstack/issues/43#issuecomment-308273958







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 4 at 13:20









                Freid001Freid001

                732826




                732826
































                    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%2f54025920%2fdocker-compose-unkown-host%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

                    Npm cannot find a required file even through it is in the searched directory