[GH-ISSUE #204] DocumentServer installed from the snap docker version in a normal user inside the docker group don't finish the installation due to an apparmor issue. #113

Author

Owner

@ShockwaveNN commented on GitHub (Dec 19, 2019):

Just checked Ubuntu 18.04 with docker from snap and everything working fine.

Did other containers run normally on your system?
I think it's more general problem related with AppArmour settings, maybe this helps
https://docs.docker.com/engine/security/apparmor/

@ShockwaveNN commented on GitHub (Dec 19, 2019): Just checked Ubuntu 18.04 with docker from snap and everything working fine. Did other containers run normally on your system? I think it's more general problem related with AppArmour settings, maybe this helps https://docs.docker.com/engine/security/apparmor/

kerem commented

Author

Owner

@EchedelleLR commented on GitHub (Dec 19, 2019):

Thank you for your help, I will check it but for the next time if I test a raw installation in a specific OS I would expect help on the same and not "similar" or "equivalent" taking in account they could have changes in configurations (and they have them) by default.

@EchedelleLR commented on GitHub (Dec 19, 2019): Thank you for your help, I will check it but for the next time if I test a raw installation in a specific OS I would expect help on the same and not "similar" or "equivalent" taking in account they could have changes in configurations (and they have them) by default.

kerem commented

Author

Owner

@EchedelleLR commented on GitHub (Dec 19, 2019):

Checking the output from the user where it is running:

Running /sbin/apparmor_parser apparmor_parser --version it throws

AppArmor parser version 2.13.2
Copyright (C) 1999-2008 Novell Inc.
Copyright 2009-2018 Canonical Ltd.

/usr/share/apparmor-features/features file exists without any issue and I can check it from that user.

@EchedelleLR commented on GitHub (Dec 19, 2019): Checking the output from the user where it is running: Running /sbin/apparmor_parser apparmor_parser --version it throws > AppArmor parser version 2.13.2 > Copyright (C) 1999-2008 Novell Inc. > Copyright 2009-2018 Canonical Ltd. /usr/share/apparmor-features/features file exists without any issue and I can check it from that user.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 19, 2019):

@EchedeyLR If you wanna quick help you can always attach virtualbox, qemu or other image with your OS in which problem is reproduces

@ShockwaveNN commented on GitHub (Dec 19, 2019): @EchedeyLR If you wanna quick help you can always attach virtualbox, qemu or other image with your OS in which problem is reproduces

kerem commented

Author

Owner

@EchedelleLR commented on GitHub (Dec 19, 2019):

I don't think it is possible in an ADSL2+ connection.

I have no issues to wait but I prefer that if anyone provides feedback about it, was in the same conditions.

@EchedelleLR commented on GitHub (Dec 19, 2019): I don't think it is possible in an ADSL2+ connection. I have no issues to wait but I prefer that if anyone provides feedback about it, was in the same conditions.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 19, 2019):

@EchedeyLR If you provide instruction which you used to Install Debian 10 on raw I'll try to reproduce your problem.

P. S. I'm interested in reproducing your problem, but I don't think it's a good idea to point out to people how to do their job

@ShockwaveNN commented on GitHub (Dec 19, 2019): @EchedeyLR If you provide instruction which you used to `Install Debian 10 on raw` I'll try to reproduce your problem. P. S. I'm interested in reproducing your problem, but I don't think it's a good idea to point out to people how to do their job

kerem commented

Author

Owner

@EchedelleLR commented on GitHub (Dec 19, 2019):

I don't think it's a good idea to point out to people how to do their job

I recognize this. Sorry for that.

I used the CD-1 to install Debian and in the part related to install desktop and create a normal user I unchecked them.

@EchedelleLR commented on GitHub (Dec 19, 2019): > I don't think it's a good idea to point out to people how to do their job I recognize this. Sorry for that. I used the CD-1 to install Debian and in the part related to install desktop and create a normal user I unchecked them.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 19, 2019):

@EchedeyLR Any special setup for AppArmour? I'll not able to use real PC to install Debian, but try on VirtualBox

@ShockwaveNN commented on GitHub (Dec 19, 2019): @EchedeyLR Any special setup for AppArmour? I'll not able to use real PC to install Debian, but try on VirtualBox

kerem commented

Author

Owner

@EchedelleLR commented on GitHub (Dec 19, 2019):

No, I just installed snap after the installation and docker, I forgot to add the "reboot" step between install snap and install docker from it.

@EchedelleLR commented on GitHub (Dec 19, 2019): No, I just installed snap after the installation and docker, I forgot to add the "reboot" step between install snap and install docker from it.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 19, 2019):

@EchedeyLR I was able to reproduce on debian-10.1.0-amd64-netinst.iso image with all updates to 10.2

docker: Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `/sbin/apparmor_parser apparmor_parser --version` failed with output: Failed to load features from '/usr/share/apparmor-features/features': No such file or directory

Now we try to figure something out :)

@ShockwaveNN commented on GitHub (Dec 19, 2019): @EchedeyLR I was able to reproduce on `debian-10.1.0-amd64-netinst.iso` image with all updates to 10.2 ``` docker: Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `/sbin/apparmor_parser apparmor_parser --version` failed with output: Failed to load features from '/usr/share/apparmor-features/features': No such file or directory ``` Now we try to figure something out :)

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 19, 2019):

Did other containers run normally on your system?

You didn't answer or I missed, but on my system
docker run hello-world cause same error, seems this error not related to ONLYOFFICE

@ShockwaveNN commented on GitHub (Dec 19, 2019): > Did other containers run normally on your system? You didn't answer or I missed, but on my system `docker run hello-world` cause same error, seems this error not related to ONLYOFFICE

kerem commented

Author

Owner

@EchedelleLR commented on GitHub (Dec 19, 2019):

Sorry, I didn't and I recognize my fault reporting this here instead of test other container and report it to docker snap.

@EchedelleLR commented on GitHub (Dec 19, 2019): Sorry, I didn't and I recognize my fault reporting this here instead of test other container and report it to docker snap.

kerem commented

Author

Owner

@EchedelleLR commented on GitHub (Dec 19, 2019):

Anyways, thank you for your help to reproduce the issue and identify it.

@EchedelleLR commented on GitHub (Dec 19, 2019): Anyways, thank you for your help to reproduce the issue and identify it.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 19, 2019):

@EchedeyLR you're welcome, if you want I can report issue at snapcraft forums. I mean if you not going to do it by yourself. I think we should report it

@ShockwaveNN commented on GitHub (Dec 19, 2019): @EchedeyLR you're welcome, if you want I can report issue at snapcraft forums. I mean if you not going to do it by yourself. I think we should report it

kerem commented

Author

Owner

@EchedelleLR commented on GitHub (Dec 19, 2019):

The issue affects to OnlyOffice too, so of course.

I already opened a new topic there and I am waiting to know which should I provide. If I need some help with it or they provide any specific information about the issue I will try to post it here.

@EchedelleLR commented on GitHub (Dec 19, 2019): The issue affects to OnlyOffice too, so of course. I already opened a new topic there and I am waiting to know which should I provide. If I need some help with it or they provide any specific information about the issue I will try to post it here.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Dec 19, 2019):

@EchedeyLR could you attach link to topic?

@ShockwaveNN commented on GitHub (Dec 19, 2019): @EchedeyLR could you attach link to topic?

kerem commented