devcontainer

Example devcontainer for work with libfn/functional.

Useful if your operating system does not directly support the compiler required by libfn/functional.

Security note

This devcontainer does not create a user account inside the container, and hence it could create a security risk. The recommended way to use it is with a rootless docker or podman (which is always rootless). The rootless mode will map the container root account into the host account of the user running the container (rather than the host root account), hence removing the risk.

The failure to use the devcontainer in rootless mode will make the host root account an owner of all the files created inside the devcontainer, making it difficult to manage the development workspace on the host, and possibly creating other risks.

The recommended way to use this repo is by creating its fork first.

Within own fork, users can add a non-root user to the container and manage the security risk this way.

Content

This devcontainer is based on the official gcc container, with the addition of clang packages and other development tools.

Most elements inside the container are subject to taste, for example:

• selection of vim editor
• selection of zsh shell
• grml shell customizations
• ccache being used and its cache location ~/.ccache
• aliases defined in ~/.zprofile
• location of ~/venv
• etc.

Similarly most elements of devcontainer.json are subject to taste, for example:

• selection of vscode plugins
• ccache_data volume
• bind point for /tmp
• bind point for $SSH_AUTH_SOCK
• etc.

For this reason, it is not recommended to use this repo as-is. Instead, the users are expected to fork this repo, apply customizations as needed, and then use it. In case of a fault being found in this repo, pull requests will be welcome.

If you use this repo, it is your responsibility to know what you are doing.

There are no explicit or implicit guarantees of any kind, not even usefulness or basic security.

License

This repo does not contain source code of a computer program. However, for the avoidance of doubt, it is explicitly put in the public domain with the Unlicense

Future changes

It is likely that the structure or content of this repo will significantly change over time, with no guarantees of any stability (e.g. regarding the available devcontainer functionality, devcontainer compatibility, file locations etc.).

If you like it, fork it.