• [6.8.0] docker --link kills container => command failed

    ukkeman

    By ukkeman

      • Minor

    Im losing one container after another on auto updates.

    I just found out about it today.

      

    /usr/bin/docker: links are only supported for user-defined networks.
See '/usr/bin/docker run --help'.

The command failed.

     

    I don't want to generate a network for  a mysql machine where all the container accessing this machine are in the same network and also do not really like the cli way of adding custom networks.

    This is why i liked the linking.

     

    Is there another way or do i miss something?
    Going back to 6.7.2 for now and will report back if this is only a 6.8.0 issue

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    S1dney

    I had the same.

    Docker links are deprecated though.. https://docs.docker.com/network/links/
    I solved it by creating a network for the container.

     

    I believe you "can" still use it by omitting the --net switch on your command, which will link it to the default bridge network:

    https://github.com/docker/cli/issues/2030

     

    However it's deprecated for a reason 🙂

    Note that this does require running a command to create the docker container cause the --net switch will be fed to docker deamon through DockerMan if using the GUI.

    Edited by S1dney
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.