티스토리 뷰
docker: Error response from daemon: service endpoint with name {randomName} already exists.
소농배 2019. 5. 29. 18:48batch was fail every 4~5 times per day
all of fail reason are same.
docker: Error response from daemon: service endpoint with name {randomName} already exists. |
common error alarm make developer insensitive batch fail.
root cause of above error is docker bridge network connection is still connected even docker container removed.
for long term, we should check why bridge connection is alive even docker container removed. but batch slave is used by several team.
It is difficult to clarify which team batch makes above issue.
So, i decided to assign docker name to clarify vendor batch make zoombie bridge connection or not and to escape random name already exist error.
bash shell for generate container name
runningTimeStamp=`/bin/date +%Y%m%d%H%M%S` jobName="$JOB_NAME" containerName="$jobName-$runningTimeStamp"
docker run --name $containerName ..... |
'Trouble Shooting' 카테고리의 다른 글
Spring Cloud Gateway Redirect 시 호스트 변경됨 (0) | 2020.11.29 |
---|---|
갑자기 AWS 인스턴스 재부팅 됨 (Suddenly AWS instance was rebooted) (0) | 2020.04.18 |
Java AbstarctMethodError (1) | 2020.03.09 |
Java DateTimeFormatter 저장 오류 (0) | 2019.05.29 |
Hibernate toString stackOverflowError (0) | 2019.05.29 |
- Total
- Today
- Yesterday
- Seperate Chaining
- notify()
- reative
- Flux
- AbstractMethodError
- custom config data convertion
- mariadb-connector-j
- mariada-connector
- Lazy
- ConcurrentHashMap
- HashMap
- notifyAll()
- referencedColumnName
- MariaDB
- GlobalFilter
- N+1
- reactor
- circurit breaker
- RoutePredication
- rate limit
- router
- aurora
- RouteDefinition
- ResultSet
- getBoolean
- msyql-connector-java
- DyanomoDB
- wait()
- dynamodb
- spring cloud gateway
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |