After Docker extension upgrade to 1.6.3 version all containers are automatically published to 127.0.0.1 on host

Follow

Comments

7 comments

  • Avatar
    Unknown User

    It is insane that this could be allowed to happen without warning 

    3
    Comment actions Permalink
  • Avatar
    Wolfgang Vieregg

    Honestly, in my perspective as a DevOps, you guys have made a real super mess for the customer. It would be nice to know why you lock something so we have to unlock it in the console even though we didn't want to, almost everyone uses Docker so the services are accessible from the outside.

    3
    Comment actions Permalink
  • Avatar
    SwiftInternet Support

    That caused a few hours of confused trouble shooting during the night... can we ensure the option is not re-added on the next update please.

    3
    Comment actions Permalink
  • Avatar
    Francesco Bancalari

    Guys I've lost about 3 hours caused by the update released this night. 
    Plesk extension for docker v. 1.6.4 claims to revert changes made by v 1.6.3 but it simply does not.

    I had to manually edit config file as per Ivan's instructions above. 
    Thanks Ivan, you saved my day. 


    IMHO things like this should never happen in a production scenario like this.

    2
    Comment actions Permalink
  • Avatar
    Anonymized user

    We have a bunch of docker containers running, and it took a while to figure out that the problem was not the update of the container but with docker. I'm baffled how this passed by even a minimum of QA.

    And to only get a "reverted the changes" in the change log (when looking at the docker extension in Plesk) without explaining that the issue may persist without a link to this article is another major screw-up... please do better in the future.

    1
    Comment actions Permalink
  • Avatar
    Oliver Burkill (Edited )

    Lots of people using public IP in config even if it's a local connection. Often to a redis container for sessions, their sites logins and carts will be broken but may not trigger any monitoring they have as site will still respond ok. What a mess.

    Are you going to revert this with another update? edit: seen sense there...

    edit: It was no accident, it's documented in the release notes!  did no one think what would happen? (https://docs.plesk.com/release-notes/obsidian/change-log/#docker-1.6.3)

    1
    Comment actions Permalink
  • Avatar
    Benjamin Boy (Edited )

    How could you push such an update automatically to all world? This is an catastrophic failure of QOS. Im really upset.

    Why didnt you made the update so that everyone can choose either the container binds to local or public interface?

    1
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request