注意：
The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "LXD/FAQ"
< LXD
Jump to navigation
Jump to search
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
These are some questions that are frequently asked about LXD and related technologies. | These are some questions that are frequently asked about LXD and related technologies. | ||
# Can I use storage backend other then directory, that doesn't support some features? | |||
#* This could be circumvented by using a image file and formatting it with btrfs and using that as storage pool. | |||
# I can see all 80 cores with lscpu, are they all available? | # I can see all 80 cores with lscpu, are they all available? | ||
#* No, unfortunately you can use only the number of cores that you have paid with your subscription. | |||
No, unfortunately you can use only the number of cores that you have paid with your subscription. | # Is my container directly bound to specific CPU cores? | ||
#* No, we limit only the number of cores for the container, but don't specify which cores are bound to your container. | |||
*# | # Are the settings made through "lxc config edit" - boot persistent? | ||
#* Yes, they are. | |||
# Is it possible to put multiple lines for example for lxc.raw config? | |||
#* Yes, it is possible with: raw.lxc: |- lxc.mount.entry = none dev/shm tmpfs rw,nosuid,nodev,create=dir, lxc.mount.entry = none tmp tmpfs rw,nosuid,nodev,create=dir | |||
# How to make mounted directories writeable inside the container? | |||
#* Change of user and group is needed to match the uid/gid of the container. | |||
# How can I connect to screen inside container? | |||
#* This can be done for example: lxc exec fun -- sh -c "exec >/dev/tty 2>/dev/tty </dev/tty && /usr/bin/screen -s /bin/bash" or lxc exec fun -- sh -c "exec >/dev/tty 2>/dev/tty </dev/tty && /usr/bin/screen -x" or use tmux :) | |||
Latest revision as of 20:14, March 8, 2018
These are some questions that are frequently asked about LXD and related technologies.
- Can I use storage backend other then directory, that doesn't support some features?
- This could be circumvented by using a image file and formatting it with btrfs and using that as storage pool.
- I can see all 80 cores with lscpu, are they all available?
- No, unfortunately you can use only the number of cores that you have paid with your subscription.
- Is my container directly bound to specific CPU cores?
- No, we limit only the number of cores for the container, but don't specify which cores are bound to your container.
- Are the settings made through "lxc config edit" - boot persistent?
- Yes, they are.
- Is it possible to put multiple lines for example for lxc.raw config?
- Yes, it is possible with: raw.lxc: |- lxc.mount.entry = none dev/shm tmpfs rw,nosuid,nodev,create=dir, lxc.mount.entry = none tmp tmpfs rw,nosuid,nodev,create=dir
- How to make mounted directories writeable inside the container?
- Change of user and group is needed to match the uid/gid of the container.
- How can I connect to screen inside container?
- This can be done for example: lxc exec fun -- sh -c "exec >/dev/tty 2>/dev/tty </dev/tty && /usr/bin/screen -s /bin/bash" or lxc exec fun -- sh -c "exec >/dev/tty 2>/dev/tty </dev/tty && /usr/bin/screen -x" or use tmux :)