You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The creds_file option seems to be used for both image and chef_image (presumably data_image, too), which fails when mixing and matching registries.
Ideally, I think we'd want to be able to specify credentials for multiple repositories, similar to a ~/.docker/config.json. (Even better if it could read this file directly rather than managing a separate creds.json.
Retries to auth and pull from chef/chef end up burning through my DockerHub rate limit 😅
❯ kitchen create def
-----> Starting Test Kitchen (v3.2.2)
-----> Creating <default-ubuntu-1804>...
/opt/chef-workstation/embedded/lib/ruby/gems/3.0.0/gems/lockfile-2.1.3/lib/lockfile.rb:308: warning: finalizer references object to be finalized
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 1 actions failed.
>>>>>> Failed to complete #create action: [{"message":"Head \"https://registry-1.docker.io/v2/chef/chef/manifests/17\": toomanyrequests: too many failed login attempts for username or IP address"}
] on default-ubuntu-1804
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration
➕ Additional context
Totally possible I'm doing things wrong. Only related thing I see is #126. Thanks in advance!
The text was updated successfully, but these errors were encountered:
👻 Brief Description
The
creds_file
option seems to be used for bothimage
andchef_image
(presumablydata_image
, too), which fails when mixing and matching registries.Ideally, I think we'd want to be able to specify credentials for multiple repositories, similar to a
~/.docker/config.json
. (Even better if it could read this file directly rather than managing a separatecreds.json
.For example:
Version
kitchen-dokken (2.17.0)
Environment
MacOS (M1), Docker 20.10.12
Scenario
chef/chef
image from DockerHub as the defaultchef_image
my.private-registry.com/my-custom-image
by setting a customimage
in driver configWhen passing a creds file, the initial pull of
chef/chef
fails. When not specifying a creds file, I cannot pull my custom image.Steps to Reproduce
kitchen create default
with the following.kitchen.dokken.yml
creds.json
:Expected Result
Instances is created successfully.
Actual Result
Retries to auth and pull from
chef/chef
end up burning through my DockerHub rate limit 😅➕ Additional context
Totally possible I'm doing things wrong. Only related thing I see is #126. Thanks in advance!
The text was updated successfully, but these errors were encountered: