How to disallow push to docker repository

I am currently setting up a local cluster at my work using docker. Basically everything works fine, the only thing I worry about is, that other devs that use my setup may eventually push the local builds to a remote repository.

Since this would be a catastrophe because we are not allowed to upload the companies artefacts anywhere else than internal servers – is there a way to prevent other users from pushign to a remote docker repo?

  • Docker. How to get bash\ssh inside runned container (run -d)?
  • Docker COPY not updating files when rebuilding container
  • Building the MongoDB Docker image
  • Mesos, Docker and GRE Tunneling
  • Advice needed on how to setup a SAAS service for a php based application
  • Is Docker complementary or competitive to Spring Boot / Dropwizard? [closed]
  • How can you push using git to a Docker Cloud Repo?
  • How to pass a parameter to docker with kubernetes
  • Among Kubernetes, OpenShift, Docker Swarm and Docker DataCenter deployment tools which all are having automatic rollback?
  • SSH to backend app
  • How can I debug my docker container with phpStorm
  • How to include files outside of Docker's build context?
  • One Solution collect form web for “How to disallow push to docker repository”

    docker repo == docker registry?

    Not sure I get the full picture about your desired workflow, but here are two options:

    • Use registry authentication and make sure that only authorised people push
    • Configure networking / dns / hosts to resolve to the correct registry – e.g. docker-registry.mycompany.com resolves to the local registry for devs and to the remote registry for others.
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.