dockerArchived
7 messages
All things docker
Archive: https://archive.sweetops.com/docker/
RBover 5 years ago
AWS pre-announces public container image registry - https://aws.amazon.com/blogs/containers/advice-for-customers-dealing-with-docker-hub-rate-limits-and-a-coming-soon-announcement/
RBover 5 years ago
anyone have experience with building arm containers on docker ?
i noticed that if i create a new builder, it will only be accessible under
i noticed that if i create a new builder, it will only be accessible under
root unless i ssh into my ec2 instance as my ec2-user and rerun the docker buildx create command. i'd prefer to create the builder for all users.Biswajit Dasover 5 years ago
Hello All, I have taken windows image from Docker market place. I have modified number of things manually(without docker file). Currently the container is running. I want to take the running container as
base image and start creating the docker file from it, is it possible? As i found the image in dockerbub is broken and not able to run via docker.Maarten van der Hoefover 5 years ago
https://github.com/docker/for-mac/issues/4733 for mac buyers an interesting one to follow.
mfridhover 5 years ago
Sort of related to the Docker pull rate limit recently, although that wasn't the primary reason I did it, I gathered some info and ideas from all over and set this sucker up to make my local k3d and argocd workflow bareable.... 1 minute 45 seconds instead of 12 minutes now for tearing down and bringing back up my full experimental localhost Kube stack.
https://github.com/frimik/local-docker-registry-proxy
https://github.com/frimik/local-docker-registry-proxy
Shreyank Sharmaabout 5 years ago
Hi All,
Issue with Portainer
I am facing some issues in Portainer.
It works perfectly most of the time.
But sometimes it randomly gives the following error and does not work:
After restarting the container it works fine for some days, then gives the same error.
I searched about this problem and some people are facing this problem due to their docker installation version and portainer is not at all working.
But mine is working fine and only sometimes causing problems.
Have any of you faced similar issues.
Docker version is 18..9
Portainer version is 1.23.2
docker version details:
Issue with Portainer
I am facing some issues in Portainer.
It works perfectly most of the time.
But sometimes it randomly gives the following error and does not work:
http error: Unable to initiate communications with endpoint (err=Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?) (code=500)After restarting the container it works fine for some days, then gives the same error.
I searched about this problem and some people are facing this problem due to their docker installation version and portainer is not at all working.
But mine is working fine and only sometimes causing problems.
Have any of you faced similar issues.
Docker version is 18..9
Portainer version is 1.23.2
docker version details:
Server:Engine:Version: 18.09.7API version: 1.39 (minimum version 1.12)Go version: go1.10.1Git commit: 2d0083dBuilt: Wed Aug 14 19:41:23 2019OS/Arch: linux/amd64Experimental: false