Use of "environment:" for class confinement snap

[willfaris]

While working on classic confinement snap I was exploring setting various ENV vars (basically to cajol the snap’s commands to use bundled python as opposed to the host systems python). I had success with a wrapper script but I saw references to using “environment:” in snapcraft.yam here

Libraries not found in classic snaps

oh, might that be omitted in classic snaps then? This is from corebird which I’ve not done anything special: #!/bin/sh export PATH="$SNAP/usr/sbin:$SNAP/usr/bin:$SNAP/sbin:$SNAP/bin:$PATH" export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$SNAP/lib:$SNAP/usr/lib:$SNAP/lib/x86_64-linux-gnu:$SNAP/usr/lib/x86_64-linux-gnu" export LD_LIBRARY_PATH="$SNAP/lib/x86_64-linux-gnu:$SNAP/usr/lib:$SNAP/usr/lib/x86_64-linux-gnu:$SNAP/usr/lib/x86_64-linux-gnu/pulseaudio:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH=$SNAP_L…

And there is a more specific thread here

Declaratively defining environment variables

Per the conversation in the topic about using pre-built binaries inside snaps, please note that for a some time now we support declaring environment variables to be exported inside the snap environment directly in snapcraft.yaml. For example, at the top level: environment: SOME_VAR_NAME: some value and/or under each application: apps: myapp: command: ... environment: SOME_VAR_NAME: some_value

and indeed doing something like

environment:
PATH: $SNAP/usr/bin/:$PATH

solves my problem without managing a custom wrapper script (which is nice). I am a bit worried as i cannot find a reference to “environment:” looking here https://docs.snapcraft.io/build-snaps/syntax. Is “environment:” legit, worried it might be deprecated or not fully supported. So asking is using environment: block in a snapcraft.yaml a robust solution?

Thanks

Will

[kyrofa]

We’re missing documentation for environments, indeed! Thank you for the heads up. However, yes, it is a fully-supported feature, and I am not aware of it being deprecated. Feel free to use it!