# Run with Docker Locally? - registry.hf.space

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%3E%5C
**Category:** Spaces\
**Created:** [March 31, 2023, 2:43pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198 "2023-03-31T14:43:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![iamrobotbear](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/iamrobotbear/32/14097_2.png) [@iamrobotbear](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fiamrobotbear)%5C
**Post date:** [March 31, 2023, 2:43pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%2F1 "2023-03-31T14:43:48Z")

</div>

![CleanShot 2023-03-31 at 07.38.51@2x](https://us1.discourse-cdn.com/hellohellohello/original/2X/7/7bb85c92ce2d705961c3ee645bba655681a2131d.jpeg)

Which credentials are we supposed to use here? docker login registry.hf.space

My Docker hub credentials don’t work, the Huggingface login credentials don’t work, I literally do not know what to do.

Thanks!

---

<div class="post-metadata">

**Author:** ![osanseviero](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/osanseviero/32/38738_2.png) [@osanseviero](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fosanseviero)%5C
**Post date:** [March 31, 2023, 4:24pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%2F2 "2023-03-31T16:24:31Z")

</div>

Hey there! Sorry for the issue, we need to clarify better. Your credentials should be:

Username: hugging face username  
Password: An access token from your settings page

---

<div class="post-metadata">

**Author:** ![iamrobotbear](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/iamrobotbear/32/14097_2.png) [@iamrobotbear](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fiamrobotbear)%5C
**Post date:** [March 31, 2023, 5:47pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%2F3 "2023-03-31T17:47:47Z")

</div>

@osanseviero omg, thank you, this isn’t documented ANYWHERE as far as I can tell.

Now to figure out why none of the spaces I’ve tried allow it to work…

6ae770d6091b: Download complete  
5ec58819c216: Download complete  
1abaf77c7bc2: Download complete  
86043062ced9: Download complete  
65f692d82037: Download complete  
8c5ed5b26834: Download complete  
4d09f00857ba: Download complete  
3dd0caf39ec0: Download complete  
795768a1f135: Download complete  
8edeac37e1d7: Download complete  
91ce43dd5db1: Download complete  
docker: failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header.  
See ‘docker run --help’.

---

<div class="post-metadata">

**Author:** ![osanseviero](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/osanseviero/32/38738_2.png) [@osanseviero](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fosanseviero)%5C
**Post date:** [March 31, 2023, 6:08pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%2F4 "2023-03-31T18:08:13Z")

</div>

Yes, you need to set containerd as mentioned in the page

> You need to switch on the new containerd engine in Docker for pulling and storing images. This will be the new Docker default in the future. Read more

If that does not work, I would also suggest to use the latest Docker Desktop version as we use some features that are in beta.

---

<div class="post-metadata">

**Author:** ![lowlypalace](https://avatars.discourse-cdn.com/v4/letter/l/f08c70/32.png) [@lowlypalace](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Flowlypalace)%5C
**Post date:** [April 17, 2023, 9:45am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%2F5 "2023-04-17T09:45:13Z")

</div>

I’m facing the same issue as @iamrobotbear

```auto
fb668870d8a7: Pull complete 
8a612414e2bc: Pull complete 
2c12f5dee74d: Pull complete 
e8b64516db7f: Pull complete 
5063cc75a5fc: Pull complete 
0b5eea1e39eb: Pull complete 
19026083d6ce: Pull complete 
9ec6d9577f70: Pull complete 
4d04e22a64a3: Pull complete 
c89166c8ea49: Pull complete 
76b0ea444c14: Pull complete 
bc5a04c3e525: Pull complete 
0f63c1049832: Extracting 263.3MB/263.3MB
942948180013: Download complete 
f192ca193561: Download complete 
689017106e43: Download complete 
9b47ef56fce2: Download complete 
4f941b704304: Download complete 
46995db4b389: Download complete 
0566a60652fd: Download complete 
a627c5514c75: Download complete 
2663a1b669bf: Download complete 
docker: failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header.

```

A few other users mentioned the same error on Linux / OS X in this Twitter thread:

> <https://twitter.com/huggingface/status/1641029818635493382>

---

<div class="post-metadata">

**Author:** ![efsokmen](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@efsokmen](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fefsokmen)%5C
**Post date:** [April 17, 2023, 5:37pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%2F6 "2023-04-17T17:37:34Z")

</div>

Hi,

I was having a similar problem with running the image [http://registry.hf.space/csuhan-llama-adapter:latest](http://registry.hf.space/csuhan-llama-adapter:latest) besides other images.

The error was always the same: “Error processing tar file(exit status 1): archive/tar: invalid tar header” in the last stage of the download.

FYI it was not a login issue, I had already logged in to my huggingface account and I am running this on a virtual instance, in Debian 10 setting.

I could solve this error by correctly installing dockers on the instance, following the guidelines given in [Install Docker Engine on Debian | Docker Documentation](https://docs.docker.com/engine/install/debian/) .

---

<div class="post-metadata">

**Author:** ![xieydd](https://avatars.discourse-cdn.com/v4/letter/x/90ced4/32.png) [@xieydd](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fxieydd)%5C
**Post date:** [June 20, 2023, 2:47am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%2F7 "2023-06-20T02:47:47Z")

</div>

still have the issue, link [Failed to pull images from registry.hf.space](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ffailed-to-pull-images-from-registry-hf-space%2F43853)

---

<div class="post-metadata">

**Author:** ![jurassicpark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@jurassicpark](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fjurassicpark)%5C
**Post date:** [August 17, 2023, 6:57am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frun-with-docker-locally-registry-hf-space%2F35198%2F8 "2023-08-17T06:57:43Z")

</div>

I solved this error by reinstalling docker with the latest version on ubuntu 20.04.

> **[Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/)**
>
> Jumpstart your client-side server applications with Docker Engine on Ubuntu. This guide details prerequisites and multiple methods to install.
