docker is a direct bash alias for podman. so i suppose it works with podman.
Then inside the onedev docker container :
$ podman container exec -it onedev bash
root@a66d63f5e98c:/# echo "mypasswd" | docker login -u mylogin --password-stdin
Error response from daemon: login attempt to https://index.docker.io/v1/ failed with status: pinging container registry index.docker.io/v1/: invalid status code from registry 404 (Not Found)
It does not work from inside the onedev container
I also run container list from insde to check if docker.sock is always valid
# root@a66d63f5e98c:/# docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a66d63f5e98c 1dev/server:7.9.12 "/root/bin/entrypoin…" 3 days ago Up 3 days 127.0.0.1:6610->6610/tcp onedev
everything is fine.
--
Maybe a podman issue, i will investigate.
If you have a idea...
Robin Shen commented 1 year ago
Looks like a podman compatiblity issue to me. I tried to run docker login in below container and it reports the same error:
podman run -it --rm -v $XDG_RUNTIME_DIR/podman/podman.sock:/
var/run/docker.sock docker sh
While this works fine:
docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock docker sh
Robin Shenchanged fields1 year ago
Name
Previous Value
Current Value
Type
Bug
Support Request
Robin Shen commented 1 year ago
A workaroung might be to login outside OneDev container beforehand.
I setup a specific job executor with docker registry login/pass to publish my image.
It used to work before but no more, seems to be a regression ?
screenshoot attach
PS: i test my login/passwd in the main docker hub, it works.
thanks for you help