Having the job id as environmental variable in the container

This might already exist but I didn’t find it.

It would be great if one could access the job id of the run inside the container itself as environmental variable, similarly to e.g. $SLURM_JOB_ID for slurm.
Other variables might also be useful, like where the dataset or result folder was mounted. For me, the job id would be enough to know.