Pebble, workload container and environment variables

Hello Jon,

Just to fully understand the behavior.

When you say:

the environment variables set in pebble are only set for those processes that pebble starts.

that means if I have the following layer:

            "services": {
                "mysql": {
                    "override": "merge",
                    "summary": "mysql daemon",
                    "command": "docker-entrypoint.sh mysqld",
                    "startup": "enabled",
                    "environment": {
                        "MYSQL_ROOT_PASSWORD": self.mysql_root_password,
                    },
                },
            },

Is Pebble starting docker-entrypoint.sh mysqld?

If so, shouldn’t the command "docker-entrypoint.sh mysqld" get the environment variable?

My issue here is that I need that docker-entrypoint.sh gets the variable, so if I can set the variable in the container is ok for me.