question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deploying with Docker fail, .ssh/config file bad owner.

See original GitHub issue

I checked that…

  • … the documentation does not mention anything about my problem
  • … the problem doesn’t occur with the default MkDocs template
  • … the problem is not in any of my customizations (CSS, JS, template)
  • … there are no open or closed issues that are related to my problem

Description

Deploying with Docker fails. I bind the .ssh directory with ssh config file.

The log says:

Bad owner or permissions on /root/.ssh/config
fatal: Could not read from remote repository.

Please make sure you have the correct access rights

Actual behavior

I have 600 file permission (.ssh/config file) and the owner it’s me (not root). I try to change file permission and it doesn’t work, but after changing the owner to root it works. For the rest of files I’m still the owner.

Expected behavior

Work with the original configuration, i.e. being me the owner of config file.

Steps to reproduce the bug

Docker run comand:

docker run -it -v ~/.ssh:/root/.ssh -v  ~/.gitconfig:/root/.gitconfig -v ${PWD}:/docs squidfunk/mkdocs-material gh-deploy -m "Test"

Package versions

I am using the 5.1.5 version of squidfunk/mkdocs-material image.

System information

I don’t think this is relevant, but I put it anyway.

  • OS: Fedora 30

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
squidfunkcommented, May 16, 2020

Yes, if you figure it out, I would encourage you to post your solution here 😊

1reaction
tzinmcommented, May 9, 2020

This is a general Docker problem and you seem to be quite proficient in Docker. Could I ask you to investigate yourself and share your findings?

Fine, I wil investigate about this “issue” 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

2 ways to fix bad owner or permissions on SSH config
1. Change permission ; Right-click the .ssh folder and click Properties.
Read more >
Bad Owner or Permissions on SSH Config Windows 10
The error above states the issue: Permissions for the key file are too open. It is required that your private key files are...
Read more >
Ask Question - Stack Overflow
However its giving me the Bad owner or permissions on /root/.ssh/config error. From what I've figured, docker is running as my ubuntu user...
Read more >
Search - appsloveworld.com
Coding example for the question Docker Bad owner or permissions on /root/.ssh/config-docker.
Read more >
Ask Question - Server Fault
I needed to have rw for user only permissions on config. This fixed it. chmod 600 ~/.ssh/config. As others have noted below, it...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found