Read on Twitter
I'm running the Ubuntu 20.04 beta and have been using #LXD for my dev work on 16.04/18.04.
It's awesome -- LXD has a permanent spot in my dev toolbox now. Highly recommended for library/ #ROS package maintainers who work across distros.
Some tips
It's awesome -- LXD has a permanent spot in my dev toolbox now. Highly recommended for library/ #ROS package maintainers who work across distros.
Some tips
1) For working with #ROS in LXD, check out this primer by @rhys_the_davies: https://ubuntu.com/blog/ros-development-with-lxd
2) Create a baseline image and set up your env (dotfiles, packages, tools). Use `lxc publish` and save a snapshot. Base future containers off this image, and you're already set up.
I also did this for each #ROS distro I use - no need to re-install for new containers.
I also did this for each #ROS distro I use - no need to re-install for new containers.
3) I added this to my .bashrc:
lxcsh() { lxc exec "$1" -- sudo --login --user ubuntu; }
Which makes getting a shell in a container easier. Or just use SSH.
Credit: https://discuss.linuxcontainers.org/t/logging-in-a-container-as-a-normal-user/190
lxcsh() { lxc exec "$1" -- sudo --login --user ubuntu; }
Which makes getting a shell in a container easier. Or just use SSH.
Credit: https://discuss.linuxcontainers.org/t/logging-in-a-container-as-a-normal-user/190
4) Using vim/tmux/emacs works great obviously.
If terminal work isn't your cup of tea, the #VSCode remote-SSH extension works great, including the integrated terminal: You can do things like `code <filename>` and have them open up in the editor. Applies beyond LXD of course.
If terminal work isn't your cup of tea, the #VSCode remote-SSH extension works great, including the integrated terminal: You can do things like `code <filename>` and have them open up in the editor. Applies beyond LXD of course.
