#docker (2020-11)

docker

All things docker

Archive: https://archive.sweetops.com/docker/

2020-11-01

2020-11-03

RB avatar
Advice for customers dealing with Docker Hub rate limits, and a Coming Soon announcement | Amazon Web Servicesattachment image

Many container customers building applications use common software packages (e.g. operating systems, databases, and application components) that are publicly distributed as container images on Docker Hub. Docker, Inc. has announced that the Hub service will begin limiting the rate at which images are pulled under their anonymous and free plans. These limits will progressively take […]

1
Matt Gowie avatar
Matt Gowie

Yeah, interested in the public registry bit… I wonder how they’ll run that.

Advice for customers dealing with Docker Hub rate limits, and a Coming Soon announcement | Amazon Web Servicesattachment image

Many container customers building applications use common software packages (e.g. operating systems, databases, and application components) that are publicly distributed as container images on Docker Hub. Docker, Inc. has announced that the Hub service will begin limiting the rate at which images are pulled under their anonymous and free plans. These limits will progressively take […]

Matt Gowie avatar
Matt Gowie

AWS released their Public registry detection tool — https://github.com/awslabs/aws-container-images-toolkit

awslabs/aws-container-images-toolkit

A collection of tools to statically and dynamically identify public container images that are hosted on Docker Hub. - awslabs/aws-container-images-toolkit

2020-11-04

2020-11-10

RB avatar

anyone have experience with building arm containers on docker ?

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.

RB avatar

not sure how to create the builder for all users but if we know the name of the user that will use it, it can be done using the runuser command

runuser -l myuser -c 'docker run --privileged --rm tonistiigi/binfmt --install all'
runuser -l myuser -c 'docker buildx create --platform linux/amd64,linux/arm64,linux/arm/v7 --name mybuilder --use'
runuser -l myuser -c 'docker buildx inspect --bootstrap'

2020-11-11

Biswajit Das avatar
Biswajit Das

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.

roth.andy avatar
roth.andy

It is possible, but not recommended.

https://docs.docker.com/engine/reference/commandline/save/

Instead, reproduce the steps you took in a Dockerfile so that they can be repeated when a new image is built.

docker save

docker save: Produces a tarred repository to the standard output stream. Contains all parent layers, and all tags + versions, or specified repo:tag, for each argument provided.

roth.andy avatar
roth.andy

sorry, not save. docker commit is the command to use

roth.andy avatar
roth.andy
docker commit

docker commit: It can be useful to commit a container’s file changes or settings into a new image. This allows you to debug a container by running an interactive shell,…

2020-11-12

maarten avatar
maarten

https://github.com/docker/for-mac/issues/4733 for mac buyers an interesting one to follow.

Docker fails to launch on Apple Silicon · Issue #4733 · docker/for-mac

Fails to launch on Apple Silicon (unsurprisingly given it's so new). Can't see a similar issue so raising here to track. I have tried with the latest version of my channel (Stable or Edge) …

2
Maciek Strömich avatar
Maciek Strömich

not really. this ticket is mainly about DTK which did not support virtualization. M1 does and it’s just a matter of dev time when Docker will be able to run on new macs. The more interesting question is whether Docker will be able to run x86 images.

Docker fails to launch on Apple Silicon · Issue #4733 · docker/for-mac

Fails to launch on Apple Silicon (unsurprisingly given it's so new). Can't see a similar issue so raising here to track. I have tried with the latest version of my channel (Stable or Edge) …

mfridh avatar

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

frimik/local-docker-registry-proxy

Local Docker registry proxy. Contribute to frimik/local-docker-registry-proxy development by creating an account on GitHub.

1
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
Docker fails to launch on Apple Silicon · Issue #4733 · docker/for-mac

Fails to launch on Apple Silicon (unsurprisingly given it's so new). Can't see a similar issue so raising here to track. I have tried with the latest version of my channel (Stable or Edge) …

Maciek Strömich avatar
Maciek Strömich
Apple Silicon M1 Chips and Docker - Docker Blogattachment image

Learn from Docker experts to simplify and advance your app development and management with Docker. Stay up to date on Docker events and new version announcements!

2020-11-16

2020-11-17

2020-11-24

Shreyank Sharma avatar
Shreyank Sharma

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: 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.7 API version: 1.39 (minimum version 1.12) Go version: go1.10.1 Git commit: 2d0083d Built: Wed Aug 14 19:41:23 2019 OS/Arch: linux/amd64 Experimental: false

    keyboard_arrow_up