dirrrr
(Dirrrr)
November 2, 2022, 8:02am
1
Hi there,
Could someone explain how pipe works in this docker file for example →
https://hub.docker.com/layers/jenkins/inbound-agent/4.10-3-alpine/images/sha256-32de6179e6fea169f409f272284ceb523c50190660f45bd320a6f07d355aeec2?context=explore
In lines 8,9, 13, 19 for example RUN command starts with |5 or |2 I don’t get it.
Any explanation will be much appreciated!
Thanks
meyay
(Metin Y.)
November 2, 2022, 7:00pm
2
What you shared is not a Dockerfile.
The Dockerfile(s) responsible to build the image are:
# The MIT License
#
# Copyright (c) 2015-2020, CloudBees, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
This file has been truncated. show original
# The MIT License
#
# Copyright (c) 2015-2020, CloudBees, Inc. and other Jenkins contributors
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
This file has been truncated. show original
and probably containers/Dockerfile.releases.full at main · adoptium/containers · GitHub
None of those Dockerfiles use pipes in the sense you refered to. There is nothing to get, this is just the build history, and those pipes and numbers are added by Buildkit. I have no idea what they mean, but it is nothing ment to be used in a Dockerfile.
2 Likes
dirrrr
(Dirrrr)
November 3, 2022, 7:08am
3
Hi Metin,
Thanks for the reply. It was strange to me as well I have a case where the new inbound agent is missing curl, which I guess is normal.
Anyway thanks for your investigation!