---
title: "Discussion on \"How to prevent field splitting when using ENV variables in Docker ENTRYPOINT\" | Hashnode"
description: "Discussion on \"How to prevent field splitting when using ENV variables in Docker ENTRYPOINT\". By default, variables will be split by space characters. This is not what you want if you have a message that contains spaces for example.\nTo prevent this, the variable may be surrounded by quotation marks. If you’re using the exec form in the ENTRYP..."
url: "https://hashnode.com/posts/how-to-prevent-field-splitting-when-using-env-variables-in-docker-entrypoint/608c335cdc886b43180043d3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How to prevent field splitting when using ENV variables in Docker ENTRYPOINT](https://thoeny.dev/how-to-prevent-field-splitting-when-using-env-variables-in-docker-entrypoint?utm_source=hashnode&utm_medium=feed)

By default, variables will be split by space characters. This is not what you want if you have a message that contains spaces for example. To prevent this, the variable may be surrounded by quotation marks. If you’re using the exec form in the ENTRYP...

Nov 15, 2020 · 1 min read · thoeny.dev  
Read the article

-   [#docker](https://hashnode.com/tag/docker)
-   [#shell](https://hashnode.com/tag/shell)

## Written by

[Orlando Thöny](https://hashnode.com/@orlandothoeny)

@orlandothoeny · Zürich, Switzerland

  
[View profile](https://hashnode.com/@orlandothoeny)

Software Developer & DevOps Engineer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.