docker 报错 error checking context: ‘no permission to read from ‘/home/velscode/.bash_history‘‘

最新推荐文章于 2023-05-29 01:20:23 发布

原创最新推荐文章于 2023-05-29 01:20:23 发布 · 2.3k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#docker #bash #容器

错误现象

执行docker build时报错

velscode@velscode:~$ docker build -f Dockerfile . -t ubuntu/test:1.0
error checking context: 'no permission to read from '/home/velscode/.bash_history''.

错误原因

docker在build时会尝试对整个目录进行tar压缩,包括.开头的文件。我在主目录~进行build操作，而目录下的.bash_history没有执行权限，因此报错

解决方法

在~下新建一个空目录，在这个目录里执行即可

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

velscode

关注关注

2
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

【Docker】docker build: Error checking context is accessible: ‘no permission to read from ‘proc/sys/ne

A-Itfuture的博客

10-18

416

docker build报错： Error checking context: ‘no permission to read from ‘/proc/sys/net/ipv4/route/flush’’. 不要在系统根目录下制作镜像。

docker build： Error checking context is accessible: 'no permission to read from 'proc/sys/net/ipv4/r

coco32123的博客

06-28

2885

docker build报错解决：不要再/下制作镜像。

参与评论您还未登录，请先登录后发表或查看评论

解决you have no permission to access this repo fatal: Could not read from remote repository

dqchouyang的专栏

05-29

662

用他人的秘钥通过SecureCRT工具导入到电脑中时，相当于在电脑的内存中，用写的秘钥覆盖了原来的秘钥，结果导致原来的秘钥在使用的时候认证不通过。提示的错误很清晰，这里要说明一下我的账号不叫aaa，所以，在遇到这个错误之后，我赶紧回忆从昨天（因为昨天还是可以提交代码的）到今天，我都干了哪些事是与aaa这个人相关的。很快想到，今天在登录其他项目的时候，使用了SecureCRT（类似xshell的工具）配置了远程服务器的一个秘钥（id_rsa）文件，现在想想，这个文件的主人，应该叫aaa。

Docker学习笔记：docker build error checking context: 'can't stat '\\?\D:\System Volume Information''.

OceanSky的专栏

11-28

3347

Here are my steps on Windows 10 that worked. Open Command Prompt Window as Administrator cd c:\users\ashok\Documents mkdir dockerfiles cd dockerfiles touch dockerfile notepad dockerfile # ...

Dockerfile的使用以及docker部署java项目

热门推荐

gangye19970101的博客

09-03

2万+

DockerFile定制一切 docker可以利用简单的编写程序构建出任何你想要的环境，同时可以跟业务代码相结合，快速构建和生成所需要的应用。 Dockerfile用来创建一个自定义的Image，包含了用户指定的软件依赖等。使用Docker的build命令可以直接构建新的Image。它简化了从头到尾的流程并极大地简化了部署工作。一、Dockerfile语法 Dockerfile语法由两部分构成：注释和命令+参数简单示例：构建一个简单的镜像 Dockerfile可以将文件名字设置为Docker

shell enter: -d uc926 emulator voip PLATFORM=emulator DOCKER: -- Checking for module 'x11' -- No package 'x11' found -- Checking for modules 'gtk+-2.0;gthread-2.0' -- No package 'gtk+-2.0' found -- No package 'gthread-2.0' found CMake Error at src/CMakeLists.txt:19 (MESSAGE): Gtk+-2.0 not found -- Configuring incomplete, errors occurred! See also "/home/mary/VOIP/voip/gvfb/CMakeFiles/CMakeOutput.log". make: *** 没有指明目标并且找不到 makefile。停止。 try to launch docker with platform emulator WARNING: Error loading config file: /home/mary/.docker/config.json: open /home/mary/.docker/config.json: permission denied

06-19

我们正在解决一个复杂的系统配置问题，涉及Docker、CMake、GTK+依赖和权限问题。用户提供的命令是`shellenter-duc926emulatorvoipPLATFORM=emulator`，但遇到了多个错误：CMake配置错误（GTK+-2.0未找到，X11相关包...

nonobody@nonobody-Legion-R7000-ARP8:~/catkin_ws$ source devel/setup.bash nonobody@nonobody-Legion-R7000-ARP8:~/catkin_ws$ roslaunch grid_path_searcher demo.launch ... logging to /home/nonobody/.ros/log/fc9f499a-81b6-11f0-9e67-337946b96f37/roslaunch-nonobody-Legion-R7000-ARP8-4628.log Checking log directory for disk usage. This may take a while. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. started roslaunch server http://nonobody-Legion-R7000-ARP8:45899/ SUMMARY ======== PARAMETERS * /demo_node/map/margin: 0.0 * /demo_node/map/resolution: 0.2 * /demo_node/map/x_size: 20.0 * /demo_node/map/y_size: 20.0 * /demo_node/map/z_size: 10.0 * /demo_node/planning/start_x: 0.0 * /demo_node/planning/start_y: 0.0 * /demo_node/planning/start_z: 1.0 * /random_complex/CircleShape/lower_circle_rad: 0.6 * /random_complex/CircleShape/upper_circle_rad: 2.0 * /random_complex/ObstacleShape/lower_hei: 1.0 * /random_complex/ObstacleShape/lower_rad: 0.1 * /random_complex/ObstacleShape/upper_hei: 3.0 * /random_complex/ObstacleShape/upper_rad: 0.7 * /random_complex/init_state_x: 0.0 * /random_complex/init_state_y: 0.0 * /random_complex/map/circle_num: 40 * /random_complex/map/obs_num: 300 * /random_complex/map/resolution: 0.1 * /random_complex/map/x_size: 20.0 * /random_complex/map/y_size: 20.0 * /random_complex/map/z_size: 10.0 * /random_complex/sensing/rate: 0.5 * /rosdistro: noetic * /rosversion: 1.17.4 * /waypoint_generator/waypoint_type: manual-lonely-way... NODES / demo_node (grid_path_searcher/demo_node) random_complex (grid_path_searcher/random_complex) waypoint_generator (waypoint_generator/waypoint_generator) ROS_MASTER_URI=http://localhost:11311 ERROR: cannot launch node of type [grid_path_searcher/demo_node]: Cannot locate node of type [demo_node] in package [grid_path_searcher]. Make sure file exists in package path and permission is set to executable (chmod +x) ERROR: cannot launch node of type [grid_path_searcher/random_complex]: Cannot locate node of type [random_complex] in package [grid_path_searcher]. Make sure file exists in package path and permission is set to executable (chmod +x) process[waypoint_generator-3]: started with pid [4642] roslaunch grid_path_searcher demo.launch

08-26

我们正在解决ROS中出现的错误：`ERROR: cannot launch node of type [grid_path_searcher/demo_node]: Cannot locate node`。这个错误通常发生在启动launch文件时，ROS无法找到指定的节点。根据引用[1][2][3]中的...

Started by user wangyanan Running as SYSTEM Building in workspace /var/lib/jenkins/workspace/wyn-tomcat The recommended git tool is: NONE using credential f2d4bc93-a0cb-47be-9179-43abb24c18bf > git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/wyn-tomcat/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://192.168.200.20:3000/wyn/wyn.git # timeout=10 Fetching upstream changes from http://192.168.200.20:3000/wyn/wyn.git > git --version # timeout=10 > git --version # 'git version 2.18.1' using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://192.168.200.20:3000/wyn/wyn.git +refs/heads/*:refs/remotes/origin/* # timeout=10 Seen branch in repository origin/master Seen 1 remote branch > git show-ref --tags -d # timeout=10 Checking out Revision bb82c0c7268211c47ac8286190bfb535e0b5d80f (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bb82c0c7268211c47ac8286190bfb535e0b5d80f # timeout=10 Commit message: "first wyn commit" > git rev-list --no-walk bb82c0c7268211c47ac8286190bfb535e0b5d80f # timeout=10 [wyn-tomcat] $ /bin/sh -xe /tmp/jenkins9892240535786796116.sh + docker rm -f tomcat01 permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Delete "http://%2Fvar%2Frun%2Fdocker.sock/v1.45/containers/tomcat01?force=1": dial unix /var/run/docker.sock: connect: permission denied Build step 'Execute shell' marked build as failure Finished: FAILURE

06-10

在使用 Jenkins 进行 Docker 构建时，如果遇到 `/var/run/docker.sock: permission denied` 的错误，通常是由于 Jenkins 用户没有权限访问 Docker 套接字文件 `/var/run/docker.sock`。以下是详细的解决方法： ####...

Running with gitlab-runner 18.2.1 (cc489270) on build runner DRD3psNWE, system ID: r_GbGl5uElIfib Preparing the "shell" executor 00:00 Using Shell (bash) executor... Preparing environment 00:00 Running on 13eb81186604... Getting source from Git repository 00:02 Gitaly correlation ID: 01K32MQ4SKE83SGNZ0ZME7ERJY Fetching changes with git depth set to 20... Reinitialized existing Git repository in /home/gitlab-runner/builds/DRD3psNWE/0/devsecops/cachecloud/.git/ Checking out 95d64101 as detached HEAD (ref is main)... Skipping Git submodules setup Executing "step_script" stage of the job script 00:00 $ echo "do opensca scan..." do opensca scan... $ /root/.config/opensca-cli/opensca-cli -path $CI_PROJECT_DIR -token xxxxxxxxxxxxxxxxx -out $CI_PROJECT_DIR/results/result.html,$CI_PROJECT_DIR/results/result.dsdx.json bash: line 156: /root/.config/opensca-cli/opensca-cli: Permission denied Cleaning up project directory and file based variables 00:00 ERROR: Job failed: exit status 1

08-21

或者，在安装opensca-cli时，使用非特权用户可访问的目录（如$HOME/.local/bin，但注意这里$HOME是Runner用户的家目录，而不是/root）。 3. 如果必须在root目录下安装，则需要在作业中切换为root用户执行（不推荐...

Started by user huzng Running as SYSTEM Building in workspace /var/jenkins_home/workspace/dcloud-short-link-account The recommended git tool is: NONE using credential 1f0bf418-ebd2-4381-9ec9-090e12e122ea > git rev-parse --resolve-git-dir /var/jenkins_home/workspace/dcloud-short-link-account/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gitee.com/huzng0816/dcloud-short-link.git # timeout=10 Fetching upstream changes from https://gitee.com/huzng0816/dcloud-short-link.git > git --version # timeout=10 > git --version # 'git version 2.39.5' using GIT_ASKPASS to set credentials gitee凭证 > git fetch --tags --force --progress -- https://gitee.com/huzng0816/dcloud-short-link.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 Checking out Revision 06a132ebd53b4aedcf207fa67ef4431ebb9dda4e (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 06a132ebd53b4aedcf207fa67ef4431ebb9dda4e # timeout=10 Commit message: "打包配置" First time build. Skipping changelog. [dcloud-short-link-account] $ /bin/sh -xe /tmp/jenkins3295438651166041262.sh + echo 登录阿里云镜像登录阿里云镜像 + docker login login --username=huzng crpi-cgofe8pfpyt8kzhw.cn-shenzhen.personal.cr.aliyuncs.com --password=Hzh728675. /tmp/jenkins3295438651166041262.sh: 3: docker: Permission denied Build step 'Execute shell' marked build as failure Finished: FAILURE