Tried on the exact same ubuntu build, works fine to me... so I would still guess it's a local config problem
Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-54-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage * MicroK8s 1.15 is out! Thanks to all 40 contributors, you get the latest greatest upstream Kubernetes in a single package. https://github.com/ubuntu/microk8s user@nuc:~$ git clone https://github.com/suntong/squid-alpine-ssl.git Cloning into 'squid-alpine-ssl'... remote: Enumerating objects: 7, done. remote: Counting objects: 100% (7/7), done. remote: Compressing objects: 100% (6/6), done. remote: Total 50 (delta 1), reused 4 (delta 0), pack-reused 43 Unpacking objects: 100% (50/50), done. user@nuc:~$ cd squid-alpine-ssl/ user@nuc:squid-alpine-ssl$ docker-compose up Creating network "squidalpinessl_default" with the default driver Pulling squid-alpine-ssl (alatas/squid-alpine-ssl:latest)... latest: Pulling from alatas/squid-alpine-ssl c67f3896b22c: Pull complete 440e6ed511b8: Pull complete 847023064f29: Pull complete a9feff2a3c77: Pull complete 76bf3e160a3a: Pull complete 24048ab52d48: Pull complete 39519a455c0c: Pull complete Digest: sha256:9c80c62244e3c703b6870d39d95b1bfd3c9c4906a7011bc6563701bc63af81e6 Status: Downloaded newer image for alatas/squid-alpine-ssl:latest Creating squidalpinessl_squid-alpine-ssl_1 ... Creating squidalpinessl_squid-alpine-ssl_1 ... done Attaching to squidalpinessl_squid-alpine-ssl_1 squid-alpine-ssl_1 | Starting squid... squid-alpine-ssl_1 | Preparing folders... squid-alpine-ssl_1 | Creating certificate... squid-alpine-ssl_1 | Generating a 2048 bit RSA private key squid-alpine-ssl_1 | .......................................................+++++ squid-alpine-ssl_1 | ..........................+++++ squid-alpine-ssl_1 | writing new private key to '/etc/squid-cert/private.pem' [...etc...]
Oh, thanks a lot for the confirmation! Didn't realize that the same ubuntu build can have so different results. Now I know which direction to look for problems. Thanks again.
Oh, 
What version is your docker? Mine:
docker
$ apt-cache policy docker.io docker.io: Installed: 18.09.7-0ubuntu1~18.04.3 Candidate: 18.09.7-0ubuntu1~18.04.3 Version table: *** 18.09.7-0ubuntu1~18.04.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 100 /var/lib/dpkg/status 17.12.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages $ docker version Client: Version: 18.09.7 API version: 1.39 Go version: go1.10.1 Git commit: 2d0083d Built: Wed Jul 3 12:13:59 2019 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.09.7 API version: 1.39 (minimum version 1.12) Go version: go1.10.1 Git commit: 2d0083d Built: Mon Jul 1 19:31:12 2019 OS/Arch: linux/amd64 Experimental: false
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Tried on the exact same ubuntu build, works fine to me... so I would still guess it's a local config problem
Oh, thanks a lot for the confirmation! Didn't realize that the same ubuntu build can have so different results. Now I know which direction to look for problems. Thanks again.
Oh, 
What version is your
docker
? Mine: