I don't know if this shit is expected (normal behaviour or not) but this is annoying

bash :

$ toto=tata
$ echo $toto
tata

$ toto='tata'
$ echo $toto
tata

$ toto="tata"
$ echo $toto
tata

avec docker run -e

$ docker run -e toto=tata -it debian:jessie bash
root@5de64152ed05:/# echo $toto
tata

$ docker run -e toto='tata' -it debian:jessie bash
root@99a6b62f595c:/# echo $toto
tata

$ docker run -e toto="tata" -it debian:jessie bash
root@ab7581c30734:/# echo $toto
tata

avec docker run --env-file:

$ cat env.file
toto="tata"
$ docker run -it --env-file env.file debian:jessie bash
root@805480de4a52:/# echo $toto
"tata"

$ cat env.file
toto='tata'
$ docker run -it --env-file env.file debian:jessie bash
root@004b88cc448d:/# echo $toto
'tata'

$ cat env.file
toto=tata
$ docker run -it --env-file env.file debian:jessie bash
root@2ca9908d1cdf:/# echo $toto
tata

avec docker compose:

$ cat docker-compose.yml
version: '2'
services:
foo:
image: debian:jessie
container_name: foo
environment:

• toto1=tata
• toto2="tata"
• toto3='tata'
  command: tail -f /var/log/dmesg

docker-compose up -d
docker exec -it foo bash

root@71a9a886cc24:/# echo $toto1
tata
root@71a9a886cc24:/# echo $toto2
"tata"
root@71a9a886cc24:/# echo $toto3
'tata'

TIL

Beanstalk is a little bit... magic. Dunno yet if its good or not :

Elastic Beanstalk creates log volumes on the container instance, one for each container, at /var/log/containers/containername. These volumes are named awseb-logs-containername and should be mounted to the location within the container file structure where logs are written.

For example, the following mount point maps the nginx log location in the container to the Elastic Beanstalk–generated volume for the nginx-proxy container.

{
"sourceVolume": "awseb-logs-nginx-proxy",
"containerPath": "/var/log/nginx"
}

And all this logs can be copied into s3 automagically: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-elasticbeanstalkhostmanager