Dockerfile runs on Mac but won't run on Linux behind my proxy

I have the following Dockerfile , for a container that runs just fine on my Mac, (I’m using docker-machine)

FROM perl:latest
RUN cpanm SOAP::Lite
RUN cpanm LWP::Simple
COPY . /usr/src/myapp
WORKDIR /usr/src/myapp
ENTRYPOINT [ "perl", "./doceng_purge_tools/bin/akamai_purge_pattern_generic.pl"  ]
# CMD /bin/bash
# docker build -t my_perl_purger_001 .
# docker run -t my_perl_purger_001 -pattern cd/Q14299_01 -server prod

However, when I run it using docker on my corporate network. I get a low-level SSL error.

  • Supervirsor “returning exit status 127; not expected)” on Docker
  • Docker containers with one public IP
  • How do I move where Docker Images are stored under Windows 2016
  • Dockerfile - How to pass an answer to a prompt post apt-get install?
  • Using docker/docker-machine in multiple Terminal tabs on OSX
  • Vagrant docker provisioning with env variables and network
  • Forgive my ignorance, but I thought a feature of docker is that I can be shielded from these platform gotchas.

    Is there a way I can package this up, on my Mac, and just run the container in my Linux environment, behind my firewall?

    I can supply more details about the SSL errors, if that helps.

  • Docker: google/docker-registry container usage
  • Breakpoints skipped when remote debugging with eclipse PDT and Docker container (docker for mac)
  • Replacing a particular instance on AWS Elastic BeanStalk?
  • Is docker stateless?
  • Cannot change Docker image directory
  • How can I create a Jenkins Docker image that uses provided ssh keys for jenkins user?
  • One Solution collect form web for “Dockerfile runs on Mac but won't run on Linux behind my proxy”

    … and just run the container in my Linux environment, behind my firewall?

    ...Can't connect to control.akamai.com:443 
    

    … but I thought a feature of docker is that I can be shielded from these platform gotchas.

    If you run docker behind a firewall which prohibits connections to outside you can not expect to get a connection. Docker does not create some magic tunnel through the firewall but relies instead on the existing network, same es it relies on the existence of the CPU, RAM and storage. Proper network is just another resource you need to provide for your docker image.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.