Set WORKDIR /workdir on Docker level

[abitrolly]

/workdir is a more common default working directory. At least whalebrew project uses it as a standard.

It would be nice if it /workdir is default working directory, and mount point for external files.

[tigarmo]

I personally haven't seen /workdir used much as the working directory; more commonly I've seen /app or something inside /usr/local.

Regardless, I don't see much reason to change what we use currently. Do you feel strongly about this?

[abitrolly]

@tigarmo try this - https://github.com/yakshaveinc/linux/blob/master/bin/runin-podman.sh

runin-podman.sh yakshaveinc/snapcraft:core24

This is only possible, because container uses /workdir convention. So when I have to always open GitHub page to copy paste command to run a container, I feel strongly that containers that need workdir, should have some convention.

I feel nothing wrong if all rocks used /workdir convention https://documentation.ubuntu.com/rockcraft/en/latest/explanation/rocks/#what-sets-rocks-apart

Why not /app? I may want my app to be in the container, but I probably don't want to work in its dir. The same applies to /usr/local. On Fedora I don't even have write access to that, so why I should work in this dir in the container?

Why not some other name dir? Different people may have different opinions what might go into some other name, but if the name is /workdir I guess we all agree that it only WORKDIR can go there.

[lengau]

Out of curiosity I did a couple of quick GH searches.

• WORKDIR /workdir (and variants such as WORKDIR /workdir/server) had 6.6k results
• WORKDIR /app had 680k
• WORKDIR /usr had 239k.

I also failed to find much indication that this is a common convention outside of whalebrew.

[abitrolly]

@lengau most likely /app and /usr images do not require volume mounts for standard operation, which is not the case for snapcraft. If container doesn't use volumes, /app makes a bit more sense for debugging.