This question already has answers here:
Can't apply AppArmor profile on container: "no such file or directory"
(2 answers)
Closed 2 days ago.
After a security update, OpenMediaVault 5 would not let Docker launch stacks.
Logs seems to indicate those problems comes from app-armor refusing the Docker daemon to do its thing....
Ideas ?
I tried to launch Portainer without success.
I tried to reinstall it, without success.
I rebooted a couple of times, without success.
Found this solution in Can't apply AppArmor profile on container: "no such file or directory":
I used:
sudo apt-get install apparmor-utils
sudo apt install apparmor-profiles apparmor-profiles-extra
Then I rebooted... and Docker works now.
Related
I had a working MySQL install and I tried to migrate it to MariaDB. I also have Docker, which seems to block /usr/sbin/mysqld via AppArmor.
To be clear, I’m not using Docker currently (but I’d like to not have to remove it since I will be using it soon).
The problem I’m having is when I’m trying to load my project, served by good old Apache, in the browser. I’m getting a SQLSTATE[HY000] [2002] No such file or directory error message.
The workaround right now is to force AppArmor to unblock mysqld:
sudo apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld && sudo systemctl restart mariadb
This works, but I have to redo it after every system boot.
aa-status clearly shows who the culprit is:
4 processes are in enforce mode.
...
/usr/sbin/mysqld (2960) docker-default
After running the workaround above, this line disappears from aa-status and everything works perfectly.
How can I permanently disable this "protection" from the docker-default profile?
I have attempted to install an aurora node by following the guide below:
partner-relayer-deploy
However, I am having issues. If someone could point me in the right direction that would be appreciated.
This is the first time I have used docker so perhaps I am missing something basic. However, googling and some docker youtube tutorials have not help me solve it myself.
Below is a step by step of what I have done:
Running setup.sh in gitbash shows errors but continues to install.
connection errors but continues to install
When installation is complete (75GB downloaded) I did not have docker opened so it errored as it couldn't find the daemon
Opened docker. Docker shows apps restarting
Closes setup.sh and ran again. got errors.
Additional app shown in docker
closed gitbash. Renamed 'docker-compose.yaml-mainnet' to 'docker-compose.yaml' and moved from '.contrib' folder to 'partner-relayer-deploy' folder so I could run 'docker-compose up'. Ran 'docker-compose up' got errors.
Prior to posting I have done a fresh install but am still getting the same result.
---------update-----------
I found the below issue which has prompted me to ensure my docker images are up to date
https://github.com/aurora-is-near/partner-relayer-deploy/issues/20
endpoint updated but the others were fine.
https://hub.docker.com/r/nearaurora/endpoint/tags
https://hub.docker.com/r/nearaurora/nearcore/tags
https://hub.docker.com/r/nearaurora/database/tags
I am still getting the same issue when I run setup.sh
And get the following error when I run docker-compose up
My docker command:
docker run -it --rm -v $(pwd):/mutcompute ens_net:v3
Gives me the following error:
docker: Error response from daemon: Mounts denied: approving /Users/danny/Documents/Codes/Python/net_containers/ensemble_net: file does not exist.
However, I have used this same command when in the same directory for over 6 months now. It just opens my directory in the current docker container so I can run my software that is preinstalled.
Today my docker updated to version 3.0.0 (MacOS).
I am assuming this is due to the update?
I have restarted docker and I have restarted my computer. Still does not work.
[Latest EDIT] June 8, 2021
Still not fixed, note in Docker 3.3.3 the option is no longer in Experimental features, but it's moved into General settings. Unchecking this still helps to resolve the issue. – vasek
in Docker Desktop
Open Preferences
Click General
Disable - Use gRPC FUSE for file sharing
For a lower version, see First Answer.
[EDIT] January 4, 2021
It doesn't appear to have been completely fixed yet. It is recommended to just disable it.
as described in First Answer
[EDIT] December 18, 2020
This issue is fixed in Docker 3.0.1(macOS).
Open Preferences
Click Experimental Features
Disable - Use gRPC FUSE for file sharing
Update the version to ^3.0.1
Enable - Use gRPC FUSE for file sharing
First Answer
I have the same experience after updating to Docker Desktop 3.0.0(macOS).
and solved it as below.
Open Preferences
Click Experimental Features
Disable - Use gRPC FUSE for file sharing
For windows: add a new folder path by clicking on + icon at
docker screenshot
I am relatively new for the docker technology.
Yesterday I setup docker on windows 10 machine and ran few dockers.
Today I first used command "docker system prune" so that I can run all of it once again without any conflicts.
But now I am firing below command:
docker run --name DockerName -v /c/collections:/etc/newman -t
postman/newman:ubuntu run
"MyAPITestCollection.postman_collection.json"
--environment="MyAPITestEnvironment.postman_environment.json" --reporters="json,cli" --reporter-json-export="reports/MyAPITestReport.json"
And getting below error:
error: ENOENT: no such file or directory, open 'MyAPITestEnvironment.postman_environment.json'
I haven't made any changes to the directories or anything else.
I checked the docker desktop setup option and found that the drive on which the file is located is still showing as the shared drive.
I tried by restarting the docker desktop several times and once by rebooting the machine as well but still found same error.
Kindly requesting to help me figure out the root cause of this issue and the solution as well.
My docker network had once again become public so firewall might be preventing the file access.
I changed it to private by using below command and it ran successfully:
Set-NetConnectionProfile -interfacealias "vEthernet (DockerNAT)" -NetworkCategory Private
I'm trying to use the OpenFOAM docker image. I installed everything correctly and when I try to run OpenFOAM_Start I get the error:
Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
Error response from daemon: No such container: of_1712
Error: failed to start containers: of_1712
Error: No such container: of_1712
Stopping "default"...
Machine "default" was stopped.
Then I ran docker-machine env command and I got the error:
Error checking TLS connection: Host is not running
I would appreciate if you could help me know what is the problem and how I can solve it.
P.S. Hopefully this is not off-topic. Please let me know if I should ask this question in a different stackexchange.
I found the solution but I'm still not sure what the error above mean. As indicated in the OpenFOAM installation guide, right after installation of the docker image you should run the:
"OF_Create_Env"
shortcut on the Desktop. A shell will open and close automatically,
completing setup of the user working environment. This step is mandatory
only on the first occasion of OpenFOAM for Windows installation.
Then you can run OpenFOAM_Start again and it just works.