Multiline Dockerfile syntax #1799
Comments
|
/cc @creack |
|
Fixed by #1838 |
|
+1 on that. running commands against a postgres server requires a bunch of &, && and ; and makes a really cluttered looking RUN command |
|
Anyone know how to use heredoc with this syntax? Docker wants to bunch it onto a single line and causes a bash syntax error: |
|
@d11wtq Why not just add the file instead of catting in the dockerfile? |
|
@crosbymichael because (and correct me if I'm wrong), if I edit the file (and I will), Docker won't use my edits, due to the way it caches. I could completely disable caching, but this image includes the entire llvm toolchain and is very big as it is, so I do want caching of the commands, I just need ADD to be aware of changes in the files it is adding. Maybe it already works that way, but IIRC it does not. |
|
Yes, it will use your edits. It does a checksum on the content to pick up chagnes. |
|
@crosbymichael Ah, that is excellent. Is that new? I could have sworn I'd been bitten by this in the past. That does indeed solve my issue then :) |
|
Yes as of 0.8 maybe |
|
Try this one: RUN echo 'All of your\n\
multiline that you ever wanted\n\
into a dockerfile\n'\
>> /etc/example.conf |
|
This works for me: RUN echo $'All of your\n\
multiline that you ever wanted\n\
into a dockerfile\n'\
>> /etc/example.conf |
|
And if your string contains quotes you can do this: |
No, it's not. |
|
@DevElCuy @thiagokronig What if my command contains quotes, like the following one RUN echo 'a\n\
'b'\n\
c\n'\
>> /testIt doesn't work. |
|
Would be awesome if possible to do: RUN echo $'All of your\n That is, identation in the dockerfile without getting tabs in the example.conf |
|
See #34423 |
|
I want to write a small script, so I tried: RUN echo '\n\
#!/bin/bash\n\
foo\n\
bar\n'\
> /usr/local/bin/myscript.sh
RUN chmod +x /usr/local/bin/myscript.shBut the first line is considered to be a comment, and so is ignored. Can it be escaped somehow? |
Hi, try ti add $ after the echo. |
|
It's help for me ( https://github.com/jen-soft/pydocker ) [ Dockerfile.py ] from pydocker import DockerFile # sudo pip install -U pydocker
d = DockerFile(base_img='debian:8.2', name='jen-soft/custom-debian:8.2')
d.RUN_bash_script('/opt/set_repo.sh', r'''
cat >/etc/apt/sources.list <<EOL
deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main
EOL
apt-get clean && apt-get update
''')
d.EXPOSE = 80
d.WORKDIR = '/opt'
d.CMD = ["python", "--version"]
# d.generate_files()
d.build_img()# sudo wget -qO- https://get.docker.com/ | sh
python Dockerfile.py
docker images |
|
I have tried several different varients of that |
|
Fanatics of RUN printf ''\
'#!/usr/bin/env bash\n'\
"printf 'qrcode command: qrencode -o user.png otpauth://totp/%s@%s?secret=%s'\n"\
'vsftpd /etc/vsftpd.conf'\
"${ftpuser?}" "${pasv_address?}" "${oathuser_b32seed?}" > "/usr/bin/vsftpd-docker-init"when it makes sense of course. |
|
I tried a couple of things with the echo command and could not get it to work, until I did this: It wil then show up as this: (Note the quotes) Note I did NOT use the echo $' trick, since that just inserted a $ in my code. |
|
How is it that thousands of engineers waste millions of hours on this horrible UX decision in one of the most important Free/Libre Open Source Software projects? If Docker™ are not going to fix this, then we need to just create a Dockerfile preprocessor that converts: or even into the unintelligible format that Docker™ finds superior. @jen-soft has proven this is possible. |
|
This issue is not the right place for that discussion. This is a 7 year old enhancement request, asking for
It's ironic that you mention "free/libre" and "open source", but then expect a company to do the work. This project is open source, especially so that people can participate and contribute fixes, enhancements, and features. While this project was started by "Docker™", it is driven by its maintainers, who maintain the project, and are responsible for making decisions on features and enhancements. While Docker™ pays some of their engineers to work on maintaining this project and developing features, the majority of the maintainers is not even employed by Docker.
No-one mentions it's superior; support for newlines (using Commenting on a 7 year old closed issue is not the right channel for proposing changes; to propose changes, open a new issue with a proposal. Here's a proposal that I wrote (based on some other proposals) to add support for a
Since this ticket was opened, the "builder" has been rewritten from scratch, and the next-generation builder (BuildKit https://github.com/moby/buildkit) was developed. BuildKit can both be used in Docker (currently opt-in by setting BuildKit allows adding alternative syntaxes ("front-ends") to extend the Dockerfile syntax. For example, the experimental Dockerfile syntax that is used to test / "incubate" new features in the Dockerfile syntax is distributed as a Docker image, but you could even implement your own syntax that's wholly different as Dockerfiles 9E88 . For example, if you want to build your images using a YAML file: here's a blogpost about someone creating a format called "Mockerfile"), or even build using Buildpacks. Distributing those alternative syntaxes/front-ends as images provides a mechanism to implement them without making code changes in Docker itself (they can be used on Docker 18.09 and higher when enabling BuildKit, or even older versions when using buildx) - see the "experimental" Dockerfile syntax mentioned earlier. The proposed |
|
@thaJeztah thank you very much for your great answer! |
Fixing issue with bit allocation byteoffset calculation
Dockerfile is a powerful building tool.
It will be more visually appealing adding multiline capability to it.
As example:
run /bin/echo -e '#!/bin/bash\necho This is a long
shell line; echo Next line
To detect the multiline we probably want to use a regex like '[ \t]*\n'
The text was updated successfully, but these errors were encountered: