cfergeau
commented
1 year ago From the log, the podman runtime seems to have started properly. What are you trying to do which is failing?
Closed Nanyte25 closed 1 year ago
cfergeau
commented
1 year ago From the log, the podman runtime seems to have started properly. What are you trying to do which is failing?
gbraad
commented
1 year ago As indicated in the startup log:
podman runtime is now running.
Use the 'podman' command line interface:
$ eval $(crc podman-env)
$ podman COMMANDHave you been able to do:
$ eval $(crc podman-env)
$ podman infoPlease post the results here
Nanyte25
commented
1 year ago @gbraad here you go podman info
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: connection to bastion host (ssh://core@127.0.0.1:2222/run/user/1000/podman/podman.sock) failed: ssh: handshake failed: read tcp 127.0.0.1:54852->127.0.0.1:2222: read: connection reset by peer~ podman machine list
NAME VM TYPE CREATED LAST UP CPUS MEMORY DISK SIZE
podman-machine-default qemu 2 hours ago Currently running 1 2.147GB 107.4GB
➜ ~
~ podman info
host:
arch: arm64
buildahVersion: 1.27.0
cgroupControllers:
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.0-2.fc36.aarch64
path: /usr/bin/conmon
version: 'conmon version 2.1.0, commit: '
cpuUtilization:
idlePercent: 84.56
systemPercent: 11.23
userPercent: 4.21
cpus: 2
distribution:
distribution: fedora
variant: coreos
version: "36"
eventLogger: journald
hostname: podman.crc.testing
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 5.18.18-200.fc36.aarch64
linkmode: dynamic
logDriver: journald
memFree: 15231533056
memTotal: 15574286336
networkBackend: netavark
ociRuntime:
name: crun
package: crun-1.5-1.fc36.aarch64
path: /usr/bin/crun
version: |-
crun version 1.5
commit: 54ebb8ca8bf7e6ddae2eb919f5b82d1d96863dea
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: true
serviceIsRemote: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.0-0.2.beta.0.fc36.aarch64
version: |-
slirp4netns version 1.2.0-beta.0
commit: 477db14a24ff1a3de3a705e51ca2c4c1fe3dda64
libslirp: 4.6.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.3
swapFree: 0
swapTotal: 0
uptime: 0h 0m 12.00s
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /var/home/core/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions: {}
graphRoot: /var/home/core/.local/share/containers/storage
graphRootAllocated: 32737570816
graphRootUsed: 1796513792
graphStatus:
Backing Filesystem: xfs
Native Overlay Diff: "true"
Supports d_type: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 0
runRoot: /run/user/1000/containers
volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
APIVersion: 4.2.0
Built: 1660228991
BuiltTime: Thu Aug 11 14:43:11 2022
GitCommit: ""
GoVersion: go1.18.4
Os: linux
OsArch: linux/arm64
Version: 4.2.0 ~ crc console
Only supported with OpenShift bundlesI am very confused now. ~Are you reporting for CRC or podman machine ?~ [Due to bad messaging from the client]
podman machine list
NAME VM TYPE CREATED LAST UP CPUS MEMORY DISK SIZE
podman-machine-defaultOf course we will never show up in the podman machine list, as we use a slightly different stack (utilizing native virtualization instead of Qemu).
This might be causes by the message that podman gives
Cannot connect to Podman. Please verify your connection to the Linux system using podman system connection list, or try podman machine init and podman machine start to manage a new Linux VM Please ignore these steps. /cc: @vrothberg @ashley-cui
However, from podman info I can see a connection was made as it reports:
hostname: podman.crc.testingso this seems to work.
According to the output, podman is operational.
What happens when you do:
$ podman run hello-worldAs this should give a banner output, similar to:
Resolved "hello-world" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull quay.io/podman/hello:latest...
Getting image source signatures
Copying blob a538fa3b889c done
Copying config 0411f5c56d done
Writing manifest to image destination
Storing signatures
!... Hello Podman World ...!
.--"--.
/ - - \
/ (O) (O) \
~~~| -=(,Y,)=- |
.---. /` \ |~~
~/ o o \~~~~.----. ~~
| =(X)= |~ / (O (O) \
~~~~~~~ ~| =(Y_)=- |
~~~~ ~~~| U |~~
Project: https://github.com/containers/podman
Website: https://podman.io
Documents: https://docs.podman.io
Twitter: @Podman_io
vrothberg
commented
1 year ago Can you file an issue against podman?
cgruver
commented
1 year ago @Nanyte25 I noticed that you are giving the CRC VM 15GB of RAM. Make sure you are not hitting: https://github.com/crc-org/crc/issues/3349
There is a Podman specific runtime for MacOS that does not use vfkit. It uses Qemu and is very stable on apple silicon.
brew install podman
General information
crc setupbefore starting it (Yes/No)?CRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
crc start INFO Checking if running as non-root INFO Checking if crc-admin-helper executable is cached INFO Checking for obsolete admin-helper executable INFO Checking if running on a supported CPU architecture INFO Checking minimum RAM requirements INFO Checking if crc executable symlink exists INFO Checking if running emulated on a M1 CPU INFO Checking if vfkit is installed INFO Checking if old launchd config for tray and/or daemon exists INFO Checking if crc daemon plist file is present and loaded INFO Loading bundle: crc_podman_vfkit_4.2.0_arm64... INFO Creating CRC VM for Podman 4.2.0... INFO Generating new SSH key pair... INFO CRC instance is running with IP 127.0.0.1 INFO CRC VM is running INFO Updating authorized keys... INFO Adding new bearer token for cockpit webconsole podman runtime is now running.
Use the 'podman' command line interface: $ eval $(crc podman-env) $ podman COMMAND
Expected
Actual
Logs
Before gather the logs try following if that fix your issue
Please consider posting the output of
crc start --log-level debugon http://gist.github.com/ and post the link in the issue.