classic on Fedora 28 fails: '/run/resolvconf/resolv.conf': No such file or directory

[jayvdb]

$ snap version
snap    2.27.2-2.fc28
snapd   2.27.2-2.fc28
series  16
fedora  28
kernel  4.13.0-0.rc6.git3.1.fc28.x86_64

$ sudo /var/lib/snapd/snap/bin/classic
Creating classic environment
Parallel unsquashfs: Using 4 processors
12241 inodes (13483 blocks) to write

[=======================================================================================================================================================================================================================/] 13483/13483 100%

created 9611 files
created 1459 directories
created 2541 symlinks
created 79 devices
created 0 fifos
cp: cannot stat '/run/resolvconf/resolv.conf': No such file or directory

[aduh95]

I have the same issue on Ubuntu 17.10

Is there any workaround for that?

$ snap version
snap    2.29.3
snapd   2.29.3
series  16
ubuntu  17.10
kernel  4.13.0-17-generic

[abitrolly]

The same problem in Fedora 27. Initialization fails.

✗ sudo snap run classic
Creating classic environment
Parallel unsquashfs: Using 4 processors
12189 inodes (13511 blocks) to write

[===========================================================================================================================================================================================================|] 13511/13511 100%

created 9635 files
created 1469 directories
created 2465 symlinks
created 79 devices
created 0 fifos
cp: cannot stat '/run/resolvconf/resolv.conf': No such file or directory

Then it doesn't work.

➜  ~ classic     
needs to run as root
➜  ~ sudo classic
sudo: classic: command not found
➜  ~ sudo snap run classic
cp: cannot stat '/etc/sudoers.d/*': No such file or directory

OS info.

✗ snap version   
snap    2.29.4-3.fc27
snapd   2.29.4-3.fc27
series  16
fedora  27
kernel  4.14.11-300.fc27.x86_64

[zyga]

The classic snap is meant for running something resembing classic ubuntu on a all-snap core system (typically cloud or embedded device). I don't think it makes much sense to use it on already-classic systems like Fedora or Ubuntu.

[ogra1]

The classic snap relies on a tarball inside the core snap that contains a bunch of the removed config files and such (additionally to some cached debs (apt and friends) that get installed when the classic env is created), if you would want something like this for fedora, it would have to be created in conjunction with the fedora core snap build scripts ...

regarding the issue in 17.10, please file a new issue at https://github.com/snapcore/classic-snap ... classic is based, designed and typically only run ubuntu-core 16 where resolvconf is still used, we might need some detection that we are running on a non ubuntu-core install and refuse to run at all ... (on a non-core system you should use a container or chroot, the purpose of "classic" is to provide access to classic packaging tools that you have around already.