►
Description
Blog post with insights and URLs: https://everyonecancontribute.com/post/2020-11-04-cafe-7-docker-hub-rate-limit-monitoring/
- https://about.gitlab.com/blog/2020/10/30/mitigating-the-impact-of-docker-hub-pull-requests-limits/
- https://about.gitlab.com/blog/2020/10/30/minor-breaking-change-dependency-proxy/
B
A
C
It's
a
little
bit
rainy
outside,
but
it's
fine,
so
my
name
is
mike
lagner.
I'm
a
product
manager
and
software
engineer
at
the
company
called
zkw
in
austria
we
make
headlamps
for
the
automotive
industry
and
a
part
of
the
lg
corporation
and
yeah.
We
build
high
performance
computing
stuff
in
c,
mainly
in
c
plus,
plus
c
d
engines,
ray
tracing
engines
and
so
on.
B
Okay
yeah,
my
name
is
oh,
so
my
name
is
nikka
smith,
I'm
currently
working
as
senior
dev
of
the
engineer
at
verity.
What
we
are
currently
doing
is
we
provide
detailed
identity,
cloud
solutions
for
enterprises
and
I'm
doing
there
mostly
the
platform
stuff
so
helping
our
internal
teams
to
deploy
the
application
and
also
developing
the
platform
for
the
next
generation
yeah.
So
that
would
be
my
part
mostly.
A
D
Yeah
hi,
I'm
christoph
I'm
a
senior
consultant,
I'm
mostly
a
website
guy,
but
I'm
switching
over
to
kubernetes
in
the
moment,
I'm
in
hessen
near
frankfurt,
but
yeah
born
in
bavaria.
So
I'm
still
having
his
as
a
strong
accent,
but
I
think
in
english
everybody
will
understand
so
highly
interested
in
gitlab
and
kubernetes,
but
at
the
work
or
business,
I'm
mostly
doing
other
stuff
on
deployments
and
ansible
and
and
that
stuff.
A
A
C
A
Great
thanks
again,
the
other
thing
I
kind
of
was
thinking
about
so
last
week.
We
learned
that
we
knew
it
already,
since
always
that
docker
hub
would
be
adding
the
rate
limiting
to
like
the
the
pull
requests
or
the
pulls
from
doc.
When
you
execute
a
ci
cd
job,
when
you
deploy
something
into
kubernetes,
when
you
do
something
else,
and
that's
totally
fine,
and
we
probably
should
all
be
paying
them
money
for
for
their
service.
A
But
the
thing
was,
we
were
not
sure
how
to
mitigate
that
problem
and
what
what
possible
ways
could
be
done
and,
as
things
go
along,
we
have
been
discussing
this
in
this
in.
I
think
it's
september,
in
our
german
coffee
chat
and
talking
about
like
proxiing
stuff,
caching
proxies
other
things
and
one
of
the
ideas
was
to
run
your
own
docker
registry.
Proxy
cache,
maybe
use
a
different
vendor
and
other
things,
and
we
at
gitlab
in
our
slack
channel.
A
It
was
kind
of
the
discussion
going
on
and
I
think
it
was
thursday
afternoon.
My
time
probably
said:
okay,
we
should.
We
should
do
something
about
it
because
it
we
might
be
affected
in
our
kidlet.com
shared
run
of
lead.
We
might
not
be
affected
because
we're
running
in
google
cloud
in
gcp
and
could
use
that
registry,
but
mainly
our
our
self-hosted
users
will
be
affected
and
one
of
the
things
which
resulted
out
of
that
was
or
out
of
the
discussion.
A
This
is
linked
to
the
agenda
as
well
was
that
we
found
this
is
a
blog
post
and
we
also
found
documentation
how
you
can
actually
determine
whether
you're
affected
from
the
current
rate
limit,
and
we
can.
We
learned
that
there
is
a
new
response,
header,
which
is
red
limit,
limit
and
limit
remaining
and
with
some
curl
magic.
A
You
could
obtain
an
access
token
and
later
on
use
that
for,
like
inmate
doing
a
real
pull
request,
which
kind
of
decreases
your
limit,
which
is
bad,
but
this
is
the
only
way
to
find
out
whether
you
kind
of
have
reached
the
limit
or
not,
or
you
will
be
reaching
the
limit,
and
one
of
the
things
was
okay.
Now
that
we
know
that
how
to
like
mitigate
that,
we
should
probably
also
write
down
specific
things
which
can
be
done,
and
this
was
kind
of.
A
The
second
approach
which
we
took
was
to
write
a
blog
post,
which
went
live
last
first
last
friday,
then
to
say
hey
what
what's
possible.
What
can
you
do
about
it,
especially
because
at
that
time,
when
we
discussed
that
it
was
not
clear
that
docker
will
be
soft
enforcing
the
limits,
which
is
right
now,
I
think
5
000
pull
requests
and
later
on.
It
will
be
100,
just
100.,
and
so
we
said.
A
Well,
maybe
we
want
to
use
a
registry
mirror
which
like
which
is
available,
which
situation
is
like
going
on?
What
what
can
you
do
and
and
some
like
usable
examples,
and
I
I
kind
of
figured
that
it's
a
long,
blog
post,
so
my
my
team
members
have
invested.
Basically,
it
was
a
it's
a
huge
brain
dump
and
we
are
looking
into
ways
of
like
updating
it
and
sharing
even
more
knowledge
and
another
point
we
discussed
was
here.
A
We
have
something
already,
which
is
called
the
dependency
proxy
and
and
then
I
was
like
yeah,
but
it's
just
like
it's
it's
in
the
premium
tier
right
now.
So,
if
you're,
using
gitlab
self-hosted
in
the
core
or
community
edition,
or
even
in
the
starter
version,
you
couldn't
have
access
to
that,
and
so
they,
the
quick
decision,
was
made
to
say:
okay,
we're
moving
this
to
open
source.
A
A
A
We
were
just
learning
rust,
golang
yeah,
I
kind
of
had
a
brain
block
and
it
was
like.
Oh,
I
know
python
and
I
can't
ride
python
like
when
I'm
sleeping,
and
so
it
was
kind
of
saying.
Okay,
I'm
writing
a
python
script
now
and
then
okay,
maybe
let's
just
make
it
a
monitoring
plugin-
and
this
was
kind
of
it-
was
fun
to
code
actually
and
you
can
add
it
into
a
monitoring
system.
The
only
problem
is
that
it
decreases
the
remaining
count
by
one
each
time.
A
So
it's
still
not
perfect
yet,
and
I
think
it's
worth
a
discussion
on
what
else
can
we
do?
Should
we
like?
There
was
a
challenge
discussed
at
this
discussion
on
on
twitter
yesterday.
I
think
where
I
said,
I'm
I'm
not
rewriting
that
in
rust
and
nicolas
said
yes,
challenge
accepted,
so
I'm
not
sure
if
he
will
be
writing
russ
today
or
someone
else,
or
maybe
we
don't
even
write
russ
today
I
don't
know
the
thing
is
I
want
to
learn
or
I
want
to
like
hear
from
you.
A
D
D
I'm
not
directly
affected
because
we
mostly
have
our
local
registries
running
here
for
for
kubernetes
in
the
enterprise
networks,
so
I'm
doing
mostly
stuff
for
financial
institutes
and
and
so
we
we
host
mainly
everything
on
premise
but
on
my
private
stuff,
I'm
I'm
a
little
bit
of
affected.
So
I
I
do
some
some
docker
stuff
on
my
local
machines
on
my
on
my
price
and
so
on.
D
C
D
C
So
it's
a
proxy
system
and
that
defector
has
a
nice
feature
that
you
can
go
into
the
gui
and
turn
on
the
offline
switch.
So
if
anything
goes
wrong
or
not
in
the
way
we
like,
we
have
some
kind
of
yeah
emergency
button,
so
we
can
guarantee
that
our
system
is
running
but
yeah.
We
also
now
use
the
render
everything
in
approach
and
host
it
ourselves
and
it's
it's
generally.
I
think
the
best
idea
to
host
your
important
stuff
at
your
infrastructure
and
not
relying
on
another
infrastructure
part.
C
B
So
mostly
these
changes
will
affected
all
the
ci
systems.
So
if
you
are
running
ci
systems
and
you're
using
external
images,
there
could
be
some
implications
mostly
and
for
that,
luckily,
we
in
the
company
also
using
only
all
our
own
images,
mostly
for
all
the
stuff.
So
we
have
a
simple
base
image
repository
where
we
pull
in
the
images
from
the
crop
that
we
need
to
get
everything
into
viewer.
B
But
the
hard
part
about
all
this
stuff
is
mostly
because
we're
doing
a
way
of
syncing
the
stuff
manually
is
to
updating
all
the
child
images
of
the
base
images.
So
we
have
appearance
that
has
updated
and
when
do
you
notify
them
to
update
them
all
at
once?
So
probably
you
don't
want
to
do
that
when
you
need
to
handle
at
least
50
or
100
repositories
at
one
at
once,
because
currently
everyone
doing
a
really
distributed
way
in
our
company.
So
that
means
we
have
a
lot
of
repositories
that
are
independent
from
on.
B
But
when
we
are
saying
we
are
updating
our
base
images
from
the
operations
side,
because
there
come
some
security
issue,
it
was
in
the
past.
It
was
really
hard
to
sending
a
pull
request
to
the
developers
and
open
it
to
repositories
and
notice
them
hey.
Please
update
your
base
image
because
a
new
version
comes
out,
so
this
is
another
problem.
When
you're
doing
the
stuff,
you
have
your
own
base
images
and
you
need
to
update
them
for
all
your
repositories
or
all
your
customers.
B
So
your
internal
customers,
the
different
approach
that
can
be
used
for
that
is
mostly
that
a
lot
of
people
now
recommend
to
use
is
to
using
a
proxy
so
like
you
can
use
the
dependency
proxy
in
gitlab.
You
can
use
the
if
you're,
using
only
docker
hub,
you
can
using
directly
with
the
distribution
as
pull
through
cache.
But
if
you
have
a
problem,
you
want
to
use
multiple
repositories
like
docker
hub,
google
container
registry,
and
how
does
the
code
also
try?
B
But
I
think
this
isn't
the
end
mostly
because
then
you
save
your
base
images
mostly,
but
what
you
also
need
is
to
cache
the
dependencies
in
video
privilege,
mostly
so,
for
example,
if
you're
using
a
debian
based
image,
you
should
also
test
your
pages
that
you're
currently
using
because
sometimes
it
could
be
also
happen.
That
changes
are
happen
on
the
debian
base,
if
you're
using
a
debian
based
image.
B
So
this
is
also
so
you
are
shifting
a
little
bit
of
a
problem
mostly,
and
for
that
case
you
need
also
be
ensure
that,
if
you're
using
airplane,
it's
quite
straight
away,
because
alpine
has
two
options
in
his
operating
system
by
itself,
because
you
can
package
all
your
artifacts
into
one
tar
and
can
using,
for
example,
a
simple
stretch,
image
and
then
cropping
only
the
dependencies
into
your
next
image
that
you
want
to
use
and
can
be
ensure
that
you're,
using
only
the
correct
package
versions
on
that.
Yes,
this
is
a
short
outlook.
B
So
for
that,
it's
quite
straightforward
mostly
so
this
would
be
my
it's
a
simple
approach,
but
it
says
also:
some
traffic
can
have
some
caveats.
Yeah,
probably
we'll
see
in
future
that
a
lot
of
more
companies
will
have
offer
us
a
public
registry.
So,
for
example,
ecr
will
probably
have
an
option
to
mirror
all
the
stuff.
Google
container
registry
has
also
the
option
to
mirror
all
the
images
from
all
the
sources,
but
we
will
see
probably
that
more
options
come
to
this.
B
A
different
problem
is
mostly,
then
that
we
have
a
lot
of
distributed
ways
where
we
can
get
the
images
from,
and
I'm
really
like
the
idea
that
some
people
also
propose
that
we
have
a
single
hub
where
we
can
get
all
the
images
from
this.
The
main
idea
between
weathercraft,
mostly
because
this
was
sent
for
a
place
where
you
know.
Okay,
I
don't
have
the
image
on
my
local
machine.
I
go
to
drop
looking
for
it
and
see:
okay,
here's
the
image
I
can
use
it
mostly.
B
Hopefully
we
have
some
supporters
for
that,
so
that
the
cncf
responds
like
that
or
someone
else
who
has
a
public
registry
that
can
help
us
to
reduce
the
mitigation
of
the
high
distribute
of
high
distribution
that
you
need
to
know
at
least
okay
for
this
vendor.
I
need
to
go
to
this
docker,
this
repository
url,
for
this
one
or
to
a
different
wire,
or
you
need
to
set
up
a
proxy
to
cover
the
problem
yeah,
so
that
was
a
short
artwork.
A
A
And
internally
we
also
use
harbor
for
the
images
we
use
for
our
ci
and
yeah.
We
have
different
teams
working
with
containers,
so
they
or
the
team
for
the
internal
ci
they
use,
as
other
just
said,
and
we
are
managing
our
cloud
offerings
and
we
actually
use
of
rendered
images
we
download
from
docker
hub-
and
we
use
the
ecr
at
amazon
for
these
images.
A
So
we
yeah,
we
don't
don't
know
the
images
from
docker
hub
directly
that
often
because
for
us
that,
as
part
of
our
release
process
like
we
released
our
infrastructure
code
independently
from
the
product
code,
and
yet
there
are
several
release
processes
internally
and
so
for
now
we
are
not
really
affected
because
we
do
have
the
base
images
already.
We
update
them
yeah,
not
that
often
that
200
downloads
in
six
hours,
I
think,
is
the
limit
that
this
would
affect
us
and
yep.
For
now,
we
surveyed
with
the
vmware
harbor
and
amazon.
A
C
B
B
So
that
it
won't
be
disappear
mostly
because
currently,
the
main
function
of
the
crap
is
that
you
can
easily
fetch
images
from
that
and
the
other
problem
or
not.
Problem
is
right.
Now,
if
you're,
using
the
docker
hub,
your
docker
demon
right
now,
the
docker
daemon
is
configured
to
pull
automatically
images
from
docker
hub.
So
you
can't
change
it
at
least
also
if
you
don't
recompile
your
data
demon.
B
I
think
no
one
estimated
that
it
was
so
frequently
used
so
in
terms
of
because
we
have
no
container
orchestrators.
Every
container
orchestrator
now
tries
to
fetch
all
the
images,
and
this
will
have
a
huge
impact
of
in
terms
of
traffic
and
also
probably
storing
images.
So,
as
company
view,
I
wouldn't
say
upload
your
images
to
the
doctoral
public.
B
To
probably
you
just
use
your
own
private
registry
that
you
change
over
access,
that
you
can
audit
it
who
use
it
or
who
uses
it
not,
but
the
dot
crop
is
a
great
place
easily
to
share
images
with
different
users,
because
it's
directly
integrated
in
the
dry
daemon.
So
there's
a
different
question
to
that.
B
If
you
start,
if
you're
using
docker
in
the
next
feature
for
as
a
local
developer
and
if
we
are
coming
back
from
the
idea
when
doctor
was
born,
doctor
was
mostly
proposed
for
developers,
because
it's
really
quite
easy
to
use.
You
can
easily
spin
up
containers,
so
containers
exist
before
docker.
Also,
so
google
used
antenna
since
2008
and
docker
was
400
hours
goes
into
ga
mode.
I
think
in
2015
when
when
the
1.0
reached,
so
I
think
it
won't
be
going
away
directly.
B
Probably,
but
it's
quite
more,
it's
an
interesting
point
of
view
from
the
vendor
side.
So
if
you're
selling
your
software,
how
can
I
let
my
customers
quite
easily
benefited
to
use
my
images?
So
currently
we
saw
in
the
past
already
that
because,
for
example,
elasticsearch
have
their
own
repositories,
they
don't
use
docker
hub
at
all.
B
Mostly
if
you
want
to
get
the
latest
elastic
search
image,
you
need
to
go
to
their
own
registry
to
download
it
currently
that
it's
not
so
com,
not
so
comfortable
right
now
for
the
developer,
because
you
need
to
use
a
different
url,
it's
not
so
hard
to
use
that.
But
yeah
you
lose
a
little
bit
of
confidence
and
not
not
confidence
a
little
bit
of
convincing
convenience,
mostly
so
that
it's
quite
easy
to
use
and
we
will
see
how
it
will
evolve
mostly
so.
C
B
You
know,
I
know
a
lot
of
people
that
are
using
container
d
directly
instead
of
the
docker
daemon
to
use
that,
and
also
we
have
a
different
optimized
operating
system.
So,
for
example,
like
flacca
or
container
denotes
a
translucent
stat
right
now,
yeah,
instead
right
now
by
drawers,
so
there's
a
fedora
container.
Linux
is
for
same
mostly
where
you're
running
only
the
parts
that
you're
really
needing
and
currently
they
don't
use
that
redeemer.
B
B
Probably
you
can
have
a
lot
of
more
convenience
that
the
developer
doesn't
need
to
care
about
which
url
will
be
used.
So
that
means
probably
you
need
to
have
more
rules
in
your
kubernetes
trust
or
near
container
outreach,
mostly
like
that.
So,
for
example,
like
we
have
in
development,
we
have
something
like
linting
options.
What
you
can
do
or
what
you
can't
do.
It
will
be
same
up
here
for
container
and
there
are
already
solutions
for
that.
B
For
example,
you
can
use
open
policy
agent
to
restrict
your
whole
cluster
to
say,
okay,
you
aren't
allowed
to
use
any
images
from
docker
hub
so
that
doesn't
need
to
be
technical
implementation.
So
that
means
it
doesn't
need
to
be
something
like
hey,
okay,
we're
switching
the
dns.
Are
we
shifting?
We
don't
allow
external
traffic
to
all
of
this
stuff.
We
can
use
this
in
a
more
higher
level.
So,
for
example,
we
could
use
oppa
for
that,
and
it
will
tell
us
it
would
tell
it's
for
user.
Okay,
you
shouldn't
use
this
image.
B
B
A
B
So
I
would
say
I
don't
care
at
all,
mostly,
so
I
don't
literally
decision
if
it's
docker
or
if
it's
spot
man,
I
want
to
have
a
simple
streamlined
way.
So
this
should
be
something
like
a
simple
tooling.
So
if
you
are
looking
into
bigger
enterprises,
so,
for
example,
like
we
discussed
in
the
in
the
trophy
chat
with
with
waypoint
and
so
on,
probably
there
are
some
platforms
that
support
this
and
you
don't
need
to
care
about
that
at
the
developer
at
all.
B
So
probably
you
want
to
do
only
a
git
commit
and
everything
happens
automatically.
So
this
was
where
open
shift
begins
like
in
this
way
and
also
right.
We
have
no
cloud
foundry.
What
is
a
really
bigger
platform
or
hiroku
who
doing
all
the
developer
experience
mostly.
This
comes
in
terms
of
what
is
the
feature
set
of
your
platform.
So,
as
the
operator
I
could
say,
okay,
I'm
could
be
impediment.
Okay,
should
I
stick
to
pop
man,
or
should
I
use
docker
or
should
I
use
contain
id?
B
This
comes
a
little
bit
about
stability,
and
how
is
my
experience
with
these
two
is
mostly,
but
when
you
are
looking
from
a
platform
perspective
like
like
operators,
so
currently
I
would
say:
okay,
my
platform
is
to
need
this.
I'm
currently
down
here
right
now.
What
is
the
real
container
runtime
in
terms
of
first
point
view,
but
you
need
to
care
about
that.
Probably
when
you
have
problems
in
production,
you
need
to
understand
how
potman
is
currently
working
and
how
is
how
is
docker
working
and
when
you're
going
down
the
rabbit
hole?
A
B
A
Theoretically,
it
should
work,
but
practically
I
think
there
are
some
commands
in
potman
which
are
not
implemented
right
now.
So
there
is
an
a
feature
request
for
the
gitlab
ci
runners
to
support
portman
as
an
executor,
but
I
think
something
with
pull
or
something
else
is
missing,
but
that
would
be
kind
of
like
still
me
as
a
developer,
I
don't
care
how
the
container
started
and
how
is
how
it's
executed.
A
B
B
You
know
yeah
so
yeah
right
now,
because
I
have
in
my
past
job.
I
had
a
lot
of
discussion
with
developers
and
probably,
for
example,
is
my
example.
My
persona
would
be
a
java
developer,
so
a
java
developer
as
a
java
developer.
I
want
to
develop
my
code,
and
probably
I
don't
want
to
do
the
switch
out
of
my
echo
system.
B
So,
for
example,
I
want
to
put
images
only
with
maven
or
with
how
do
they
call
gradle,
it's
mostly
the
other
famous
tool
that
you
use
as
built
system
and
probably
what
we
did
in
the
past.
So
we
shifted
all
the
docker
related
stuff
because
the
developer
don't
use
it
mostly
only
the
operators
were
using
it
and
we're
using,
for
example,
tooling,
that
integrates
directly
in
maven
and
brett,
and
for
that
something
like
a
jib
so
java
from
google
and
how
to
draw
it.
B
B
How
does
it
work?
It
works
like
because
every
image
layer
is
only
a
car
archive
mostly
and
every
image
there
has
no
own
hash
id
for
the
content,
validation.
So
every
time
you
make
a
change,
it
can
check.
Okay,
do
I
need
to
replace
the
star
archive
or
not?
So
this
is
the
idea
between
the
base
station.
B
It's
only
two
archives
and
valerian
have
been
happening
because
you
have
an
hierarchy
of
which
the
archive
needs
to
be
extracted
on
which
part,
and
for
that
this
is
the
reason
why
you
don't
need
to
try
to
build
this.
Probably
this
is
the
reason
why
people
shifting
from
dot
right
to
use
different
two
lane,
because
you
need
to
have
run
at
least
a
docker
daemon
and
the
dot
redeem
needs
to
have
root
privileges
on
your
system
to
build
a
docker
image.
B
Definitely,
but
for
that
you
can
use
altitudes
that
you,
because
we
have
now,
but
it's
important,
that
this
shift
can
only
happens
because
we
have
a
standard.
We
have
the
standard,
oci
open,
container
image,
and
this
allows
us
to
do
this
using
different
tools,
because
for
outcomes,
every
time
is
an
open
container
image.
How
does
it
draws?
I
seem
to
destroy
it
open
to
damage.
A
A
C
C
So
that
was
nicholas
is
mentioning,
is
if
you
can
switch
it.
It
depends
on
what
on
your
environment,
if
you
can
do
it
in
your
kubernetes
cluster,
then
I
would
go
this
way,
but
and
then
restrict
it.
But
at
the
end
I
would
say
if
you
have
gitlab
and
you
have
access
to
the
package
registry,
make
a
ci
chop,
build
your
image
or
or
pull
it
down
and
push
it
to.
Your
registry
is
definitely
a
good
thing
and
find
a
good
way
to
to
update
your
url
for
existing
images.
C
A
A
B
Yeah,
okay,
I
want
to
show
you
hijacking
the
part
of
what
let
me
check,
which
is
the
correct
window,
because
I
don't
want
to
share
my
4k
screen
so
that
we
need
to
dig
into
everything.
But
I
think
this
is
the
correct
one.
Okay,
mostly,
you
should
see
something
like
renovate
under
the
chord
right
yeah,
so
you
should
see
on
your
browser
with
four
tabs:
don't
okay,
yeah
literally,
like
probably
the
first
step
that
you
need
to
do
to
use
your
own
base
image
is
that
you
have.
B
The
simplest
approach
is
that
you
have
a
simple
docker
file
it
containing
the
upstream
image
that
could
be,
for
example,
here
right
now
it
could
be
alpine,
and
what
you
need
to
do
then,
is
to
probably
bring
it
with
gitlab
ci
into
your
own
registry.
So
you
have
a
simple
pipeline
job
currently
bringing
into
this
right
now
in
and
when
we
are
checking
the
operations
part,
how
was
it
yeah?
Okay?
Luckily,
we
have
now
a
lot
of
tapes
in.
A
B
Probably
what
michael
also
says
it's
quite
hard
to
update
them,
so
luckily
we
have
here
also
the
different
base,
image
versions
and
when
we
have,
for
example,
an
application
that
currently
using
this
image.
So
that
means
how
can
I
consume
all
my
own
base
images?
So
what
you
need
to
do
is
like
you
need
whoops
it's.
For
one
part,
this
is
a
different
image.
I
will
tell
you
later
why
it's
a
bit
different.
B
We
have
here
now
the
simple,
and
this
could
be
quite
tedious
to
update
this
every
time.
So
you
don't
want
to
do
this
on
your
own,
doing
it
going
out
to
your
repositories-
and
here
comes
the
cool
tool
in
that
I
found
out,
and
this
tool
called
is
called
renovate
and
renovate
can
do
a
true
job
for
you,
mostly
because
what
it
does
it
can
scan
multiple
repositories
and
checking,
for
example,
for
docker
files
and
looking
if
a
base
image
has
been
updated
or
not
and
will
create
automatically
a
pull
request.
B
So
you
can
have
also
more
configurations
in
terms
of
hey.
When
should
it
be
applied,
should
it
be
automation
to
be
rebased
when
a
new
comes
in
and
then
we
can
automatically
easily
when
we
have
a
full
automated
pipeline,
we
could
also
say,
for
example,
it
should
be
auto
merge.
So
when
our
checks
will
happen,
I
trip
merge
this
in
and
for
that
we
have
this
tool.
It
called
run
all
I
think,
and
literally
what's
really
cool
about
that.
Let
me
check.
B
It's
currently
it's
right
now,
it's
open
source,
so
you
can
use
it
on
your
own.
It
helps
you
with
automating
overdepends,
it's
not
only
for
doctor.
You
can
use
it
for
all
types
of
dependencies.
When
I
checked
into
this,
mostly,
I
found
out
that
you
can
use
a
lot
of
more
about
that.
So
in
terms
of
looking,
where
is
it
for
documentation?
B
It's
not
directly
on
the
side,
true,
I
hope
so
yeah.
So
currently
they
have
a
lot
of
not
linear
support,
so
you
can
have
different
students
which
platform
you
want
to
use
which
managers
and
managers
comes
now
in
so
which
tools
or
which
can
be
updated
automatically.
So
it
means
you
can
update
your
lhca
dependencies.
You
can
update
your
your
mpm
dependencies,
alter
also
docker
different
compose
files.
Docker
files
also
determines
what's
really
great.
B
So
then
you
would
also
take
over
problems
that,
michael
for
him
before
said,
you
can
also
use
it
to
update
your
home
requirements
and
what
you
need
to
do
to
update
this
is
really
just
straightforward,
so
I
have
a
small
image
that
it's
called
a
renovate.image.
So
this
is
currently
the
pipeline
that
I
am
currently
using
to
bit
the
image.
Okay,
I
don't
have
the
job
right
now
for
updating
the
image,
but
currently
render
weight
needs
to
be
installed,
as
is
an
mpm
package.
B
B
B
How
do
you
handle
that
currently?
What
I
did
is
by
default
all
these
managers,
so,
like
you
said,
okay,
do
I
need
to
care
about
all
the
stuff
that
currently
can
be
updated
or
not?
Right
now
you,
I
wrote
in
my
config
json
that
it
needs
only
to
check
all
the
docker
files
that
are
currently
in
the
project.
You
can
also
do
writing
your
own
radix
expressions
to
do
all
managers
that
are
not
currently
generate
built
in,
so
you
have
a
lot
of
options
to
do
that
a
little.
B
B
B
B
Let
me
check
something
okay,
so,
for
example,
I
want
to
get
the
latest
because
to
serve
contains
3.1,
I
would
say:
okay,
I
need
to
update
this
and
then
luckily
we
could
run
the
pipeline
and
so
on.
It
will
be
updated
then,
and
this
can
help
you
to
doing
the
maintenance
or
doing
all
the
toilet
work
of
regarding
updating
all
these
images
in
these
different
repositories-
and
this
is
one
point
of
getting
into
more
the
part
of.
B
B
Yeah,
so
that
would
be
my
part
on
maintaining
audiobase
images
mostly
and
then
with
the
creation
of
mica
that
he
did
so
putting
all
the
images
into
one
repository.
And
then
you
have
probably
renovate
bot
in
the
same
repository
and
running
on
a
stadium
or
when
a
new
pool
happens
and
then
sending
out
the
prs
to
all
your
repositories.
B
A
But
I
think
it's
really
great.
I
need
to
try
that
out,
especially
because,
if
we
find
a
way
to
like
propose
an
example
which
works
for
everyone,
it
should
make
it
easier
to
say:
hey,
you
follow
the
these
10
steps
and
then
you
have
your
your
own
container
registry
update
whatever
whatever
is
going
on,
because
I
can
imagine
that
yeah
this
this
could
be
a
real
problem,
so
you
first
you're
starting
with
your
boom
ubuntu
latest
and
then
you're
deciding
okay.
A
B
Quite
true
and
probably
you
can
run
it
on
same
key,
I'm
allowing
only
the
pipelines
that
have
access
to
a
trusted
registry,
so,
for
example,
it
could
be
only
that
your
ci
will
only
continue
to
work
if
it
comes
from
your
own
images
so
that
you
have
a
fast
feedback
loop
for
the
developers
or
for
yourself.
Okay,
I
don't
using
on
public
image
right
now
from
the
darker
app
and
not
from
our
own.
So
in
terms
of
compliance
and
security.
This
will
help
you
also
a
little
bit.
C
B
You
mean
something
like
this:
this
works
right
now,
okay,
so
and
then
you
can
say,
for
example,
if
you
want
to
build
a
new
image.
Currently
you
can
say
that
a
bit
and
then
I
don't
know
so
something
what's
currently
we
want
to
downgrade.
It
doesn't
make
sense
at
all,
but
you
want
to
overwrite
it
and
you
can
do
something
like
this
yeah,
but
I
don't
like
the
idea
of
that
mostly
to
do
this,
because
it's
not
written
then
into
the
ci
system,
so
you
have
no
source
of
truth
of
that.
B
So
there's
no
declarative
way.
So
I
like
more
approach
of
replacing
that
so
that
you
have
something
more.
It
could
be
something
like
this
and
then
changing
it
right
now
here,
but
for
luckily
I
found
renovate
two
weeks
ago
and
this
will
doing
most
of
the
jobs
now
from
my
side,
so
they
can
pause
on
different
tasks
instead
of
updating
images
every
week,
or
at
least
one
a
month.
B
B
B
A
B
A
Fact
this
is
about
docker
and
docker.
Actually,
but
the
thing
is,
you
can
configure
your
docker
demon
json
and
tell
it
a
registry
mirror,
which
means,
if
you
use
it
in
your
self-hosted
environment.
That's
not
not
an
issue.
This
issue
is
about
like
our
own
gitlab.com
fleet,
so
yeah
this.
This
is
one
of
the
ways
and
we
could
also
okay.
When
in
your
runner,
you
might
need
to
update
the
lookup
path
for
for
this
one.
So.
A
A
Yeah
and
just
just
to
to
remind
you
about
this
blog
post,
this
is
mainly
written
for
self-hosted
environments.
Okay,
you
could,
you
could
use
when
you're
using
gitlab.com
and
your
own
runners
in
your
own
virtual
machines.
This
applies
as
well,
but
for
for
gitlab.com
we're
using
different
methods
and
we're
using
the
gcp
cloud.
So
this
this
kind
of
puts
puts
away
some
stuff,
but
there
are
still
challenges
but
yeah.
I
would
totally
love
to
to
see
you
try
this
out
and
report
back
how
things
go.
B
C
B
A
C
A
Yeah,
so
I
will
be
like
pushing
out
the
blog
post,
maybe
this
week
about
the
monitoring
plug-in.
I
did
right.
I
will
try
some
other
mitigations
as
well
just
to
make
it
easier
because
the
curl,
the
bose
passing
thing
is
my
opinion.
Not
so
good,
and
the
other
thing
to
keep
in
mind
is
like
how
to
mitigate
it
in
a
way
of
whenever
the
ci
runner,
docker
cli,
does
something
maybe
detected
in
there.
A
A
So
even
if
you
say
hey,
I'm
I'm
getting
a
pro
tier
from
docker
hub
now,
because
I
really
want
to
pay
them
and
I
think
they
deserve
the
money.
To
be
honest,
I
still
need
to
edit
all
my
ci
configuration
because
I
need
to
add
the
toggle
login.
You
can
do
that,
but
it's
still
work.
You
need
to
like
keep
in
mind
so
like
sitting
there
and
doing
nothing
or
just
saying
hey
this,
the
soup.
We
need
a
super,
easy
solution.
B
There
are
a
lot
of
solutions,
so
many
ways
goes
through.
So
literally
there
are
a
lot
of
options
that
you
can
use,
and
mostly
you
need
to
see
if
it's
not
too
over
engineered
for
your
use
case
or
if
you
understand
it
also,
at
least
so,
there's
also
some
big
impediments,
but
I
think
they
are
the
electro
system
has
trained
for
that.
So
we
have
a
lot
of
tuning.
You
don't
need
to
rebuild.
You
don't
need
to
re
reinvent
the
wheel
all
at
once,
so
everything
is
right
now
out
there.
A
I
I
would,
I
would
add,
to
that
point
you
use
what's
there
already,
so
it
doesn't
make
sense
that
you,
for
example,
install
gitlab
now,
just
because
of
the
the
registry
you
could
probably,
but
it's
if,
if
you
already
have
a
running
system-
and
it's
like
you-
have
a
local
registry
for
something
already
try
to
go
that
approach.
If
it's
easier
for
you
to
say,
hey,
I'm
I'm
buying
a
subscription
and
it
costs
me
like
200
a
year
or
something
like
that.
A
A
Okay,
good
last
sentence:
good
luck,
sentence
famous
last
words,
and
now
production
is
burning.
No
with
that.
I
hope
that
everyone
like
found
some
some
hints
some
new
ideas.
I
will
be
publishing
the
blog
post,
I
think,
tomorrow,
on
friday
the
recording
is
already
on
youtube
either
way,
and
then
everyone
can
like
look.
Look
it
up,
look
up
the
blog
post,
the
tweets
and
so
on.