With the following Dockerfile: FROM nexylan/php-dev:7.1-alpine COPY entrypoint.sh / RUN chmod u+x /entrypoint.sh ENTRYPOINT ["/entrypoint.sh"] WORKDIR /code CMD ["tail", "-f", "/dev/null"] (The entrypoint does nothing related to the issue). The definition on docker-compose: version: '2' services: data: image: alpine volumes: - .:/code console: build: docker/php-console volumes_from: - data env_file: - .env And the following commands on Gitlab CI commands: image: docker services: - docker:dind before_script: - docker info - apk add --update bash python py-pip python-dev - pip install docker-compose - docker-compose up -d - docker-compose ps - docker-compose exec -T console make install stages: - test test: stage: test tags: [docker-privileged] script: - echo ${SSH_PRIVATE_KEY} > tests/fixtures/ssh/key - echo ${SSH_PUBLIC_KEY} > tests/fixtures/ssh/key.pub - chmod 600 tests/fixtures/ssh/* - docker-compose exec -T console ls -l tests/fixtures/ssh/ - docker-compose exec -T console chmod 777 /dev/tty - docker exec -t flintci_console_1 ssh -o StrictHostKeyChecking=no -i tests/fixtures/ssh/key -T -vvv git@github.com The SSH command is always prompting for a passphrase with the following log: OpenSSH_7.2p2-hpn14v4, OpenSSL 1.0.2k 26 Jan 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug2: resolving "github.com" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to github.com [192.30.253.112] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file tests/fixtures/ssh/key type 1 debug1: key_load_public: No such file or directory debug1: identity file tests/fixtures/ssh/key-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2-hpn14v4 debug1: Remote protocol version 2.0, remote software version libssh_0.7.0 debug1: no match: libssh_0.7.0 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to github.com:22 as 'git' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib@openssh.com,zlib debug2: compression stoc: none,zlib@openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: host key algorithms: ssh-dss,ssh-rsa debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,blowfish-cbc debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,blowfish-cbc debug2: MACs ctos: hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib,zlib@openssh.com debug2: compression stoc: none,zlib,zlib@openssh.com debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug1: kex: algorithm: curve25519-sha256@libssh.org debug1: kex: host key algorithm: ssh-rsa debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: compression: none debug3: send packet: type 30 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: Server host key: ssh-rsa SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8 Warning: Permanently added 'github.com,192.30.253.112' (RSA) to the list of known hosts. debug3: send packet: type 21 debug2: set_newkeys: mode 1 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug2: set_newkeys: mode 0 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS received debug2: key: tests/fixtures/ssh/key (0x55b4bd4e81a0), explicit debug3: send packet: type 5 debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 debug3: receive packet: type 51 debug1: Authentications that can continue: publickey debug3: start over, passed a different list publickey debug3: preferred publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: tests/fixtures/ssh/key debug3: send_pubkey_test debug3: send packet: type 50 debug2: we sent a publickey packet, wait for reply debug3: receive packet: type 60 debug1: Server accepts key: pkalg ssh-rsa blen 279 debug2: input_userauth_pk_ok: fp SHA256:3aoR/R1oBDYb0QucuGCJfBgIWW4DE2P4DjuWwgtQg/k debug3: sign_and_send_pubkey: RSA SHA256:3aoR/R1oBDYb0QucuGCJfBgIWW4DE2P4DjuWwgtQg/k Enter passphrase for key 'tests/fixtures/ssh/key': The key has no passphrase, and the same docker command works well on my local laptop, not on GitLab CI. What I'm missing?

Now I have a cluster with Rocks 5.4 based on CentOS 5.6. When I git push the code to *github.com*, I run into the errors: >error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing http://github.com/ related link: https://unix.stackexchange.com/questions/438504/compile-git-to-use-openssl-library-libssl-so-1-0-1/444718#444718 https://githubengineering.com/crypto-removal-notice/ Hope someone give a solution. Thank you very much! Qiang

I'm seeing in the **ssh_config** man page and on the **openssh** website that I should be able to use a **%n token** when locating the identity file for a given host entry. percent_expand tokens used by OpenSSH's ssh(1) and sshd(8) GitHub allows using ssh tokens as deploy tokens but prevents you from using a token more than once on multiple repositories. So I wanted to use globbing to create a single profile regardless of how many individual project keys I had to create: host github-* Hostname github.com User git IdentityFile %d/.ssh/github/%n IdentitiesOnly yes Then I put a github-MyPackage public/private key pair under the ~/.ssh/github/ directory. It finds the globbed profile and the %d works fine but if I try to do a git clone with the %n to find the Identity file name from the original command-line specified host-alias: > git clone github-MyPackage:/myorganization/MyPackage.git Cloning into 'MyPackage'... percent_expand: unknown key %n fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. This is not simply how git accesses it as it also fails with just a simple ssh command: > ssh github-MyPackage percent_expand: unknown key %n I tried googling but didn't find anything on %n. Is this not fully implemented or is there something I'm doing wrong?

I'm having an issue with GitHub Desktop when trying to clone a repo on SteamOS. It's a new Steam Deck. Fairly fresh out of the box. I installed GitHub Desktop from the Discover store. - In GitHub Desktop, I click _Clone a repository from the internet_. - It brings up a modal window entitled _Clone a repository_ - The modal has some options, I leave it set to the default of GitHub.com - The button invites me to _Sign in_ - On clicking _Sign in_ another modal invites me to sign in using my browser - On clicking _Continue with browser_ a new tab is opened in chrome (github.com/login/oauth/authorize...) - Chrome invites me to open xdg-open - When I do that I'm redirected back to GitHub Desktop. - There's an error

Can't find session /org/freedesktop/secrets/session/2

I've tried googling for an answer without success. How can I solve it?

I want to compare 6.1(which is main) and my branch git diff [6.1...] -- [/MM-pizdmr-are-up-to-date] fatal: bad revision '[6.1...]' I tried Github UI ,but it take too much time and suggested git diff 6.1.../MM-pizdmr-are-up-to-date fatal: ambiguous argument '6.1.../MM-pizdmr-are-up-to-date': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git [...] -- [...]' What is wrong wwith my diff?

when I run this command in Visual Studio Code in macOS 13.3.1, shows: ➜ texhub-web git:(main) git pull origin main fatal: unable to access 'https://github.com/RedDwarfTech/texhub-web.git/ ': LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443 this is the git config: credential.helper=osxkeychain filter.lfs.smudge=git-lfs smudge -- %f filter.lfs.process=git-lfs filter-process filter.lfs.required=true filter.lfs.clean=git-lfs clean -- %f user.name=JiangXiaoqiang user.email=jiangtingqiang@gmail.com core.ignorecase=false credential.helper=store url.https://github.com/.insteadof=git@github.com : pack.window=1 http.postbuffer=157286400 core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true core.ignorecase=true core.precomposeunicode=true remote.origin.url=https://github.com/RedDwarfTech/texhub-web.git remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* branch.main.remote=origin branch.main.merge=refs/heads/main branch.main.vscode-merge-base=origin/main lfs.repositoryformatversion=0 branch.feature/resize-flashing.vscode-merge-base=origin/main pull.rebase=false when I run this same command under iTerm, it works fine. why did this happen? what should I do to fixed this issue?

I am setting up Git usage on Raspbian. This worked OK:

cd .ssh
   ssh-keygen -t rsa -b 4096 -C "name@asdf.com"
   eval $(ssh-agent -s)
   ssh-add ./id_rsa_rpi

After I created the keys locally, I went to GitHub and added a public key there. It all worked OK, I cloned a few repositories without problems. Confirmed it all with ssh -vT git@github.com However, after a shutdown yesterday and a powerup today, git pull didn't work: git@github.com: Permission denied (publickey). I had to repeat the following:

eval $(ssh-agent -s)
ssh-add .ssh/id_rsa_rpi

Now it works again. How do I make this permanent?

Long story short I have an SSH key pair that I am copying to a new machine from a shared drive whenever the machine starts but when I load in the keys I keep getting an error. There is no difference in operating system between the machine that created the keys and the one that is using them (unsuccessfully). Load key "/root/.ssh/id_ed25519": error in libcrypto However when I then create a new SSH keypair it works perfectly fine. Is there some restrictions about copying keys or are they bound to the machine it was created on? A bit more background is that I am using this to read from my private Github repo, cp [filepath to ssh pub key on shared drive] "/root/.ssh/id_ed25519.pub" cp [filepath to ssh private key on shared drive] "/root/.ssh/id_ed25519" ssh-keyscan -t ed25519 github.com >> ~/.ssh/known_hosts chmod go-rwx /root/.ssh/id_ed25519 git clone --filter=blob:none --no-checkout git@github.com:account/repo.git I have no idea what is going on, and when i print the contents of the two key pairs they are identical, but it seems like the moment a new machine is booted it stops working - any help here would be much appreciated.

A developer wants to commit only certain files. But unable to commit as it requires clean(staged and committed all changes) working directory.

So basically I would like to create a WSL Bazzite distribution to test the Unreal Engine Cross-Compilation tools for testing. I found this container image hoping I would be able to export as a tar then import to WSL Directly unfortunately the container doesn't start for me. https://hub.docker.com/r/azuras/bazzite I was following this video for the UE 5 cross-compile functionality. https://www.youtube.com/watch?v=MVm5got0RMY Is this even possible? If so can someone explain how to convert the Bazzite ISO into a Tar for WSL Import. Thank you in advance!

Earlier today, I wanted to clone a private git repo of mine from Github and, at first, it would not work, giving me errors about ports & rejected identity. In the end, it worked out (pretty much all of a sudden, cannot say what made it work suddently) but then stopped working (of course, without any perceived changes on my side) and now I cannot get it back running. Error I get: $ git clone -v git@github.com:/.git Cloning into ''... kex_exchange_identification: Connection closed by remote host Connection closed by 140.82.121.4 port 443 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Things I checked: Pub key is added on github.com/settings/keys in the "SSH keys" section. Verified it and also tried adding "another" key with the same signature resulting in an error stating that this key had already been added. So I'm reasonably sure I've correctly added the SSH key on Github. Ensure file permissions for key are correct: $ ls -al ~ | grep ssh drwx------ 5 4096 Sep 5 18:04 .ssh $ ls -la ~/.ssh/id_rsa -rw------- 1 3434 Mär 31 2022 /home//.ssh/id_rsa Ensure SSH agent is aware of the key and has it loaded: $ ssh-add -l 4096 SHA256: (RSA) Surprisingly, before I checked, the key was not loaded and I had to load it manually, even though the key name is exactly the default name and, therefor, should have been loaded automatically - as far as I know. For reference, here's the config I'm testing with: Host ssh.github.com Hostname ssh.github.com PubKeyAuthentication yes Port 443 IdentityFile ~/.ssh/id_rsa User git Host github.com Hostname github.com PubKeyAuthentication yes Port 443 IdentityFile ~/.ssh/id_rsa User git As you can see, I've also tried with setting values directly in the config as well as running without any ~/.ssh/config at all. Check SSH connectivity: $ ssh -vvv -T -p 443 git@github.com OpenSSH_8.9p1 Ubuntu-3ubuntu0.10, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /home//.ssh/config debug1: /home//.ssh/config line 9: Applying options for github.com debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home//.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home//.ssh/known_hosts2' debug2: resolving "github.com" port 443 debug3: resolve_host: lookup github.com:443 debug3: ssh_connect_direct: entering debug1: Connecting to github.com [140.82.121.4] port 443. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home//.ssh/id_rsa type 0 debug1: identity file /home//.ssh/id_rsa-cert type -1 (several more attempts to load identity files, all fail with -1) debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10 kex_exchange_identification: Connection closed by remote host Connection closed by 140.82.121.4 port 443 Seems to me like my SSH agent is not even offering my public key but also not complaining about it missing. Any suggestions what I could check further ?

If one installs the Github Copilot software for the Vim editor, it *enables* the co-pilot by default, which could be seen as a privacy issue. I want to _disable_ the co-pilot by default and only enable it manually via :Copilot enable in the editor when needed. How may I do that?

I want to download source code from the master-next branch using git as described in the Xilinx wiki . I tried this: #git clone git://github.com/Xilinx/u-boot-xlnx/tree/master-next.git Initialized empty Git repository in /home/Hannan/master-next/.git/ fatal: remote error: Xilinx/u-boot-xlnx/tree/master-next is not a valid repository name Email support@github.com for help Even this failed: # git clone git://github.com/Xilinx/tree/master-next/u-boot-xlnx.git Initialized empty Git repository in /home/Hannan/u-boot-xlnx/.git/ fatal: remote error: Xilinx/tree/master-next/u-boot-xlnx is not a valid repository name Email support@github.com for help The command that works is: git clone git://github.com/Xilinx/u-boot-xlnx.git But how do I know that this will indeed fetch the master-next branch and not the master branch ? How do I correctly fetch a specific branch using git? I am using RHEL 6, accessed via PuTTY.

I regularly run a GUI binary through CI tests using Github Actions. Occasionally, the binary crashes unexpectedly. This issue is difficult to reproduce, so I'd like to capture a stack trace whenever it occurs. To achieve this, I'm using xvfb-run and gdb: xvfb-run --auto-servernum gdb --batch -ex "run" -ex "bt full" --args ${{github.workspace}}/src/mudlet --profile 'Mudlet self-test' --mirror However, this command always exits with code 1, which according to the xvfb-run documentation, indicates an error in the child process (gdb). I believe gdb returns this exit code because there's typically no stack trace to print. As a workaround, I've added -ex "quit 0" to the GDB command, but this prevents the workflow from failing if a genuine crash happens. How can I reliably capture a stack trace when the binary crashes and avoid workflow failures when no issues occur?

Cross-posting from [here](https://stackoverflow.com/questions/78737977/git-ls-remote-to-github-fails-with-classic-sha-1-not-supported-on-tunneled-ssh?noredirect=1#comment138823224_78737977) as suggested by the community. A bit of context: At my company we do tunneling to ssh into EC2 boxes. This tunneling command is as usual, uses ForwardAgent and the proxycommand is something like this: ProxyCommand ssh tunnelhost exec nc %h 22. Some other configs are:

AddKeysToAgent yes
UseKeychain yes
IdentitiesOnly yes
UserKnownHostsFile ~/.ssh/known_hosts
HostKeyAlgorithms +ssh-rsa,ssh-dss,ssh-ed25519
PubkeyAcceptedAlgorithms +ssh-rsa,ssh-ed25519
KexAlgorithms +diffie-hellman-group1-sha1
PubKeyAuthentication yes
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_ed25519
IdentityFile ~/.ssh/id_ecdsa

As you can see, I already tried RSA, ED25519 and ECDSA keys (all of them added to GitHub) and it seems like my key is not the issue. **The problem:** The issue is that, if I do a git ls-remote --heads git@github.com:company_org/repository.git I keep getting the error:

ERROR: You're using an RSA key with SHA-1, which is no longer allowed.
Please use a newer client or a different key type.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/  for more information.

I know my key is not SHA-1 but still keep getting this error. To confirm my theory (that my key is fine) I used (following github's guidance) the ssh -T git@github.com command and I see it's working as I receive the correct response:

Hi stoicAlchemist! You've successfully authenticated, but GitHub does not provide shell access.

I have a feeling that the server might have a conflicting config somewhere but I don't know where to look. More Context: It seems that I'm the only one on my team that is having this issue, the other engineers don't have an issue, that's why I'm leaning towards a config. I already tried changing keys, and even tried different types, changed configs to see if any of them were to blame but with no luck.

I have a github workflow that spins up a MySQL container. I'm using podman right now, because that matches our development workflow, but I'm seeing some weird differences in behavior between "podman in github actions" and "podman running on the local machine". I'm also seeing differences between "podman in github actions" and "docker in github actions". I'm installing podman in my github workflow from https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/xUbuntu_22.04 , which gets me:

Client:       Podman Engine
Version:      4.6.2
API Version:  4.6.2
Go Version:   go1.18.1
Built:        Thu Jan  1 00:00:00 1970
OS/Arch:      linux/amd64

Locally, I have a newer version of podman:

Client:       Podman Engine
Version:      5.1.1
API Version:  5.1.1
Go Version:   go1.22.3
Built:        Mon Jun  3 20:00:00 2024
OS/Arch:      linux/amd64

I'm starting mysql like this:

podman run --rm -d --name mysql -e MYSQL_ROOT_PASSWORD=secret docker.io/mysql:8

This successfully starts mysql, but the unix socket ends up in /var/lib/mysql/mysql.sock rather than /run/mysqld/mysql.sock. Unfortunately, the latter location is where everything expects to find it:

bash-5.1# mysql -u root -psecret
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
bash-5.1# ls -l /run/mysqld/
total 4
srwxrwxrwx 1 mysql mysql 0 Jun 28 01:04 mysqlx.sock
-rw------- 1 mysql mysql 2 Jun 28 01:04 mysqlx.sock.lock

In contrast, when I run the image locally, I see:

bash-5.1# ls -l /run/mysqld/
total 12
-rw-r-----. 1 mysql mysql 2 Jun 28 00:45 mysqld.pid
srwxrwxrwx. 1 mysql mysql 0 Jun 28 00:45 mysqld.sock
-rw-------. 1 mysql mysql 2 Jun 28 00:45 mysqld.sock.lock
srwxrwxrwx. 1 mysql mysql 0 Jun 28 00:45 mysqlx.sock
-rw-------. 1 mysql mysql 2 Jun 28 00:45 mysqlx.sock.lock

It's the same image in both locations. On github:

runner@fv-az730-813:~/work/workflow-test/workflow-test$ podman image ls
REPOSITORY               TAG         IMAGE ID      CREATED     SIZE
docker.io/library/mysql  8           05247af91864  9 days ago  594 MB

And locally:

$ podman image ls
REPOSITORY                                   TAG              IMAGE ID      CREATED        SIZE
docker.io/library/mysql                      8                05247af91864  9 days ago     594 MB

If I run the same image on github in docker, it works as expected:

runner@fv-az730-813:~/work/workflow-test/workflow-test$ docker exec -it mysql bash
bash-5.1# mysql -u root -psecret
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 9
Server version: 8.4.0 MySQL Community Server - GPL

Copyright (c) 2000, 2024, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>

The only difference I see is that when starting the image successfully, the following line is logged to the container output:

'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'

That line is missing when starting the container with podman in a github workflow. That comes from this section of the entrypoint script:

mysql_socket_fix() {
        local defaultSocket
        defaultSocket="$(mysql_get_config 'socket' mysqld --no-defaults)"
        if [ "$defaultSocket" != "$SOCKET" ]; then
                ln -sfTv "$SOCKET" "$defaultSocket" || :
        fi
}

And the difference boils down to the fact that running mysql --help --verbose | grep '^socket' results in this when running the container with podman locally or with docker:

bash-5.1# mysqld --verbose --help |& grep '^'socket
socket                                                       /var/run/mysqld/mysqld.sock

And this when running podman in the github workflow:

bash-5.1# mysqld --verbose --help |& grep '^'socket
socket                                                       /var/lib/mysql/mysql.sock

--- I am trying to figure out why I am seeing this difference in behavior. It *looks* like a permission problem, but I'm not sure what's causing it. In the github workflow, the runner user is able to create files and sockets in /run/mysqld without a problem when I try it manually (e.g., using nc -U /run/mysqld/foo.sock -l). --- **Update**: Here's the permission problem; running strace on the mysqld process shows:

openat(AT_FDCWD, "/etc/my.cnf", O_RDONLY) = -1 EACCES (Permission denied)

...but that doesn't make any sense:

bash-5.1# ls -l /etc/my.cnf
-rw-r--r-- 1 root root 999 Jun 21 20:50 /etc/my.cnf

And even:

bash-5.1# sudo -u mysql head -2 /etc/my.cnf
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/8.4/en/server-configuration-defaults.html 

When I run git status git doesn't show the empty directory. My remote repository is in github. Can't I add and push empty directory?

I am having problems when pulling commits from my github repository from private network (proxy, connected to it with VPN). no_proxy var in env did not help. git pull --rebase ssh: connect to host github.com port 22: Connection timed out fatal: Could not read from remote repository.

I am trying to install a package using brew but it is asking for Github username and password and failing to authenticate the connection even though I have added the ssh key to the Github. Can you suggest a way to fix this issue? Here's the response in terminal: fam007e@DarkKnightz:~$ brew tap owasp-amss/amass Running brew update --auto-update... ==> Tapping owasp-amss/amass Cloning into '/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/owasp-amss/homebrew-amass'... Username for 'https://github.com ': fam007e Password for 'https://fam007e@github.com ': remote: Support for password authentication was removed on August 13, 2021. remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication. fatal: Authentication failed for 'https://github.com/owasp-amss/homebrew-amass/ ' Error: Failure while executing; git clone https://github.com/owasp-amss/homebrew-amass /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/owasp-amss/homebrew-amass --origin=origin --template= --config core.fsmonitor=false exited with 128. fam007e@DarkKnightz:~$ ssh -T git@github.com Hi fam007e! You've successfully authenticated, but GitHub does not provide shell access.

I just wanted to raise an issue (ie. report a bug) in some software package hosted on gitlab. I have a github account, but not a gitlab one. Whenever I log in from a new device (github), I need to "authorize" the new device. Now, I tried "logging in" on gitlab using the offered github account/password authentication. I got the usual "confirm this email address" thing. I did that. Then it wanted my phone number! At this point I gave up. Do they also need my social security number, date of birth and passport number? Maybe my mother's maiden name? What's the need for all this two-factor-authentication level security?