Setting --proxy-server about dockerfiles HOT 8 CLOSED

I've been building my own images with the arguments I need, but it would be great if these images supported arbitrary arguments!

from dockerfiles.

The chrome-headless containers have CMD and ENTRYPOINT, which will allow you to add arbitrary arguments without custom builds:

from dockerfiles.

Hi, thanks very much for your answer. I tried the following:

docker run -it -p 9222:9222 --cap-add=SYS_ADMIN justinribeiro/chrome-headless "--proxy-server=64.227.8.188:8181"

but I get the error:

(google-chrome:1): Gtk-WARNING **: 07:47:48.668: cannot open display:

Do you have any idea how I could fix it...?

from dockerfiles.

Actually, even if I run the following:

docker run -it -p 9222:9222 --cap-add=SYS_ADMIN justinribeiro/chrome-headless "--proxy-server=64.227.8.188:8181" "--headless"

the container exits immediately.

from dockerfiles.

I should have been more clear: the docker documentation explains the process fully Overriding Dockerfile image defaults.

As an example, here's the container running with the full set of flags required in a pure override:

from dockerfiles.

Thanks very much for your guide, now it works fine!

In fact, I have one last question. I wonder if you know how we can add trusted certificates. I don't see a command line option for adding a certificate:

For me, using a certificate is important rather than adding simply adding the "--ignore-certificate-errors --ignore-certificate-errors-spki-list" options, because otherwise Chrome doesn't cache fetched resources (as they are untrusted)...

from dockerfiles.

The container doesn't have a means to consume custom certificates; you'd have to build your own hook to import them into the trust. If you've generated a certificate for say a local server, you can use certutil to do this on linux with something along the lines of:

$ certutil -d sql:$HOME/.pki/nssdb -A -t \"P,,\" -n ./my-local-cert.pem -i  ./my-local-cert.pem"

from dockerfiles.

I actually knew about this command, but never imagined using it inside a container to get around this issue. Thanks very much for your tip, again!

from dockerfiles.