Issue with docker/sdk up

Hi All,
Today I faced a problem while doing docker/sdk up
after docker/sdk clean
which was not there before. Btw, this is latest b2c marketplace.
Any
=> ERROR [internal] load metadata for docker.io/library/node:18-alpine 6.1s
=> CANCELED [internal] load metadata for docker.io/spryker/php:8.1 6.1s
[internal] load metadata for docker.io/library/node:18-alpine:
Dockerfile:1
1 | >>> # syntax = docker/dockerfile:experimental
2 | ARG SPRYKER_PLATFORM_IMAGE=spryker/php:7.3
3 | ARG SPRYKER_NODE_IMAGE_VERSION
ERROR: failed to solve: failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/18-alpine": remote error: tls: handshake failure
Answers
-
Heyhey,
is it still happening? Looks like a problem with ssl or similiar. This registry is not hosted by Spryker.
All the best,
Florian
0 -
Hi,
Sadly yes, this is still a problem and I'm looking for resolution.
Regards,
Piotr0 -
Can you paste the deploy file you are using here? have you tried to delete the
docker/deployment/default
folder already? (and then do the bootstrap again)0 -
I tried to recreate docker/deployment. Did not work.
Eventually I was not able to resolve the problem so, as I'm working on WSL2, I installed new Linux instance and the problem is gone now.
Unfortunately another one appeared, with downloading Blackfire. There is a problem with SSL certificate.
Is there a way to disable/remove Blackfire?
0 -
Tried to download a Blackfire outside of the image. Works without problem.
curl -A "Docker" -L https://blackfire.io/api/v1/releases/cli/linux/x86_64 --output black.tmp
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 582 100 582 0 0 2345 0 --:--:-- --:--:-- --:--:-- 2346
100 5649k 100 5649k 0 0 3058k 0 0:00:01 0:00:01 --:--:-- 4681kSo, temporarily, I fixed this by adding
—insecure
option incurl
command indocker/deployment/default/images/common/cli/Dockerfile
1 -
I read about the blackfire problem already several times. mostly related to DNS issues. After these were solved other partner devs could use it without problem. but in your case it seems to work with manual installing it which seems not related to dns then… strange, but i can sadly not reproduce it :(
0
Categories
- All Categories
- 38 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 32 Spryker News
- 536 Developer Corner
- 407 Spryker Development
- 54 Spryker Dev Environment
- 273 Spryker Releases
- 30 Propel ORM
- 46 Community Projects
- 6 Gacela Project
- 3 PHP Bridge
- 21 Hackathon
- 3.2K 📜 Slack Archives
- 115 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random
- 4 Code Testing
- 23 Product & Business Questions
- 40 Spryker Safari Questions
- 35 The Blackhole