Skip to content
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

HAVE_AUFS not defined #25

Open
bkauler opened this issue Sep 27, 2018 · 2 comments
Open

HAVE_AUFS not defined #25

bkauler opened this issue Sep 27, 2018 · 2 comments

Comments

@bkauler
Copy link

bkauler commented Sep 27, 2018

Hi,
I have a Linux kernel (4.14.71) with aufs. Overlayfs is disabled.

The pflask docs state, for the "--mount" option:

Stacks the host root_dir directory on top of the container’s dest directory using either AuFS or OverlayFS depending on what is found at compile-time.

File mount.c tests "HAVE_AUFS", however, this variable is not set anywhere. I am not familiar with Waf, looked at build/c4che/_cache.py, has a lot of variables but not HAVE_AUFS.

Do I have to explicitly set HAVE_AUFS? If so, is there a particular way to do it for waf?

Regards,
Barry

@bkauler
Copy link
Author

bkauler commented Sep 29, 2018

Hmmm, I looked back through the commits, and found that the guts of supporting aufs has been removed, even though the test for "HAVE_AUFS" is still in mount.c.

Puppy Linux and derivatives still use aufs, and that is not likely to change. I maintain Quirky Linux and EasyOS, forks of Puppy. I experimented with overlayfs about a year ago, and found a serious fault, that was not going to get fixed anytime soon -- can't recall what it was. Also, aufs supports direct writing to lower layers, which Puppy requires.

I am using pflask with the --chroot option, so it is not an issue. However, might have a look at reverting that removal of aufs, and fix it.

Just a note on the side: Puppy Linux and derivatives do not use systemd, they use the simple Busybox init.

@ghedo
Copy link
Owner

ghedo commented Oct 1, 2018

Yeah, I removed AUFS support a while ago because it was dropped from the Debian kernels and I had no way to test whether the code was still working or not (so it was basically unmaintained).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants