https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
c
I logged in as root and did a docker pull to verify Here is what I get:
Copy code
docker pull rancher/harvester-cluster-repo:v1.1.0
<http://docker.io/rancher/harvester-cluster-repo:v1.1.0|docker.io/rancher/harvester-cluster-repo:v1.1.0>: resolving      |--------------------------------------| 
elapsed: 0.4 s                                   total:   0.0 B (0.0 B/s)                                         
<http://docker.io/rancher/harvester-cluster-repo:v1.1.0|docker.io/rancher/harvester-cluster-repo:v1.1.0>: resolving      |--------------------------------------| 
elapsed: 0.6 s                                   total:   0.0 B (0.0 B/s)                                         
FATA[0000] failed to resolve reference "<http://docker.io/rancher/harvester-cluster-repo:v1.1.0|docker.io/rancher/harvester-cluster-repo:v1.1.0>": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Doesn't work: 
docker pull rancher/harvester-cluster-repo:v1.1.0
Works: 
docker pull rancher/harvester:v1.1.0
Is the 1.1.0 installed system looking for an outdated naming convention? I understand this project is in heavy development. Should I expect to be able to install and use v1.1.0?
Update: I get the same error with 1.1.1-rc2. If it matters I installed from PXE. Any guesses?
Copy code
Failed to pull image "rancher/harvester-cluster-repo:v1.1.1-rc2": rpc error: code = Unknown desc = failed to pull and unpack image "<http://docker.io/rancher/harvester-cluster-repo:v1.1.1-rc2|docker.io/rancher/harvester-cluster-repo:v1.1.1-rc2>": failed to resolve reference "<http://docker.io/rancher/harvester-cluster-repo:v1.1.1-rc2|docker.io/rancher/harvester-cluster-repo:v1.1.1-rc2>": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
p
Hi Scott, did you use ISO to install Harvester? We didn’t publish the cluster-repo image. I’ve seen a similar error when trying to do PXE installation with incorrect kernel params.
c
Hello Kiefer. I've been trying to install from the published kernel, initrd, and squash images. Like this example:
Copy code
#!ipxe
kernel harvester-<version>-vmlinuz ip=dhcp net.ifnames=1 rd.cos.disable rd.noverifyssl console=tty1 root=live:<http://10.100.0.10/harvester/rootfs.squashfs> harvester.install.automatic=true harvester.install.config_url=<http://10.100.0.10/harvester/config-create.yaml>
initrd harvester-<version>-initrd
boot
@prehistoric-balloon-31801 Along with that I didn't create or provide a configure.yaml -- I was trying to just follow the prompting.
@prehistoric-balloon-31801, I know Ubuntu and some others are able to boot from iPXE with 
root=live:<http://someserver/image.iso>
but it doesn't look like SuSE supports that.
p
Thanks Scott, could you check the 
config-create.yaml
file, missing 
install.iso_url
could lead to the issue. (https://docs.harvesterhci.io/v1.1/install/harvester-configuration#installiso_url)
c
@prehistoric-balloon-31801 That worked! It looks much more like a VM platform now and less like Rancher. 🙂 I was not using the 
harvester.install.automatic
or 
harvester.install.config_url
kernel parameters because I thought they would be optional and I could do an interactive install. My thought -- I wanted an interactive install (but from PXE) so I could see all the options and get something working. I take it that an interactive install while booting from PXE is not possible? If it's not possible, it would be good for documentation to say so. Perhaps Harvester could support a kernel parameter like 
harvester.install.iso_url
? Or the interactive installer could prompt for an iso_url?
126 Views
Open in Slack
PreviousNext
Powered by