mirror of
https://github.com/hadolint/hadolint.git
synced 2025-12-17 03:24:08 +00:00
Page:
DL3045
Pages
DL3000
DL3001
DL3002
DL3003
DL3004
DL3005
DL3006
DL3007
DL3008
DL3009
DL3010
DL3011
DL3012
DL3013
DL3014
DL3015
DL3016
DL3017
DL3018
DL3019
DL3020
DL3021
DL3022
DL3023
DL3024
DL3025
DL3026
DL3027
DL3028
DL3029
DL3030
DL3031
DL3032
DL3033
DL3034
DL3035
DL3036
DL3037
DL3038
DL3039
DL3040
DL3041
DL3042
DL3043
DL3044
DL3045
DL3046
DL3047
DL3048
DL3049
DL3050
DL3051
DL3052
DL3053
DL3054
DL3055
DL3056
DL3057
DL3058
DL3059
DL3060
DL3061
DL3062
DL4000
DL4001
DL4003
DL4004
DL4005
DL4006
Home
SC2046
SC2086
Template
No results
1
DL3045
Moritz Röhrich edited this page 2021-03-04 14:22:24 +01:00
COPY to a relative destination without WORKDIR set.
Problematic code:
FROM scratch
COPY foo bar
Correct code:
FROM scratch
COPY foo /bar
or
FROM scratch
WORKDIR /
COPY foo bar
Rationale:
While COPYing to a relative path is not problematic per sé, errors happen, when changes are introduced to the WORKDIR without updating the destination of the COPY command. Since it is easy to overlook this relationship, Hadolint emits this warning when no WORKDIR is set and COPY has a relative destination. This case is error prone and either setting the COPY-destination absolute or the WORKDIR explicitly will reduce the probability of having an error.
It is assumed, that when a WORKDIR is set, the programmer will make sure it works well together with the destination of the COPY statements.