Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #37919 Allow usage of Docker Desktop for development
    Actions
    Infos
    #37919
    Benoit Peytraud (bpeytraud)
    2024-05-23 16:07
    2024-04-30 10:44
    39523
    Details
    Allow usage of Docker Desktop for development

    We got an issue to create a development environment in docker desktop. To be precise when we want to work in a local environment, we can't have access to tuleap. So we need to add mapping ports to the docker compose to have access to tuleap.

    Empty
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Under implementation
    Empty
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #36799 Tuleap Releases 15.10 Delivered 2024-04-07 16:42 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #37919

    Git commit

    tuleap/tuleap/stable

    Chore : Docker Desktop mapping ports 2629ba6e5d
    User avatar Benoit Peytraud (bpeytraud) , 2024-05-22 17:04
    fix: Mac and Docker Desktop devs stay local e01276a786
    User avatar Manuel Vacelet (vaceletm) , 2024-05-28 17:28
    Referenced by request #37919

    Artifact Tracker v5

    rel #36799 15.10

    Other

    gerrit #31063
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2024-05-23 16:04
    • Summary
      -Docker Desktop mapping ports 
      +Allow usage of Docker Desktop for development 
    • Status changed from New to Under implementation
    User avatar
    Thomas Gerbet (tgerbet)2024-04-30 11:43

    Ideally:

    • this should be done only when the usage of Docker Desktop is detected
    • the ports should be exposed only on localhost and not to the whole world (current setup for macOS might have this issue, I think the way the port binding is handled has been modified since the moment we wrote the compose file): Docker does not care about firewalls when exposing ports and I would really like to not expose by dev stack to everything and everyone :p
    User avatar
    Benoit Peytraud (bpeytraud)2024-04-30 11:20

    On macOS of course but not on Linux. Do you have something like this on Linux ? If not, we need to make the changes on Linux.