-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Fedora images in LXD backend #48
base: master
Are you sure you want to change the base?
Conversation
|
||
if s.Distro() == Fedora { | ||
// Fedora LXD images do *not* contain tar by default, so we must install it manually | ||
args = []string{"exec", s.d.Name, "--", "dnf", "install", "--assumeyes", "tar"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, this could be done by adding tar to the fedora image setup script instead.
@@ -156,6 +221,17 @@ func isDebArch(s string) bool { | |||
return false | |||
} | |||
|
|||
func sshInstallCommand(distro Distro) []string { | |||
if distro == Ubuntu || distro == Debian { | |||
return []string{"apt", "install", "openssh-server"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be fixing Ubuntu and Debian, not Fedora, as the PR title suggests, but having spoken to people behind linux-containers.org, ssh servers are not, and won't be, installed in those images on purpose, for security reasons (default ssh server settings are often too open).
5d25cfa
to
ea89126
Compare
Snaps can't access binaries outside their shipped rootfs, so ship the lxc command in the snap. This requires that the user manually connect the lxd interface, but that's unavoidable.
Fixes #42, Fixes #44