# Docker cant log in to push to docker hub

Source: https://forum.modalai.com/topic/319/docker-cant-log-in-to-push-to-docker-hub
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2021-07-05 13:44:53 UTC by kasarrowtec
Replies: 6 · Views: 1442

## kasarrowtec · 2021-07-05 13:44:53 UTC

I am currently trying to push an image from the voxl to my dockerhub but I get an authentication error with **docker push <username>/<repository>:<tag>** we think its because of the login required to push to dockerhub. When we try and login with docker login its give us some random html back. We figured this is because of the outdated version of docker installed on the voxl or maybe the non-existent configuration file at **~/.docker/config.json.** Is there a way to push up images to dockerhub from voxl?

## Reply by Alex Kushleyev (ModalAI staff) · 2021-07-06 01:35:45 UTC

I am not sure how to resolve the authentication issue, but you can always use `docker save myimage:latest | gzip > myimage_latest.tar.gz` to a tar file, then `docker load` on another machine and push to docker hub.

Also, by the way, you can build your docker image for VOXL on a regular linux machine. Qemu allows you to emulate arm and arm64 architectures and Docker supports this. This is how the voxl-emulator runs on x86-64: So, basically you can build your docker image on a x86-64 host and then push it to docker hub or copy directly to VOXL. 

I know that does not answer your question, but hopefully there is a workaround here..

Alex

## Reply by kasarrowtec · 2021-07-07 11:39:35 UTC

Hi @Alex-Kushleyev thank you for your suggestion, yes i think this is the best way to do it. I now have the problem of clearing space on the VOXL - 

```
/dev/root       2.8G  2.7G     0 100% /
devtmpfs        1.8G     0  1.8G   0% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           1.9G  199M  1.7G  11% /run
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
tmpfs           1.9G   12K  1.9G   1% /var/volatile
/dev/sda2       2.2M   80K  2.0M   4% /persist
/dev/sde11       95M   33M   63M  35% /firmware
/dev/sde12       12M  4.1M  7.4M  36% /dsp
/dev/sda3        58M   40K   57M   1% /cache
/dev/sda9        15G  2.0G   13G  14% /data
overlay          15G  2.0G   13G  14% /data/overlay/5910e4a2f1072c4d07b9009b323563abc44fe4233641015c784491b87ad1255d/merged
shm              64M     0   64M   0% /data/containers/5910e4a2f1072c4d07b9009b323563abc44fe4233641015c784491b87ad1255d/shm
overlay          15G  2.0G   13G  14% /data/overlay/1e8a60e811f3af3eddf366c7aa8bc023352a61cc08474801d04042949a86bb75/merged
shm              64M     0   64M   0% /data/containers/1e8a60e811f3af3eddf366c7aa8bc023352a61cc08474801d04042949a86bb75/shm
overlay          15G  2.0G   13G  14% /data/overlay/cef742f165ea4745487a0b19bb599165affb1286f50a807ac64e3c547373d911/merged
shm              64M     0   64M   0% /data/containers/cef742f165ea4745487a0b19bb599165affb1286f50a807ac64e3c547373d911/shm
overlay          15G  2.0G   13G  14% /data/overlay/a4fad1d9f77bde4eb8b9f846f08f172a4d44e9ddc953a6180b7bb933fb02532f/merged
shm              64M     0   64M   0% /data/containers/a4fad1d9f77bde4eb8b9f846f08f172a4d44e9ddc953a6180b7bb933fb02532f/shm
overlay          15G  2.0G   13G  14% /data/overlay/8171bc8ce74b2b59e0cce044d397da0fe50046aaebd04e39bc184a8aaf4a2f04/merged
shm              64M     0   64M   0% /data/containers/8171bc8ce74b2b59e0cce044d397da0fe50046aaebd04e39bc184a8aaf4a2f04/shm
overlay          15G  2.0G   13G  14% /data/overlay/cf0dc03a4dfdd2107c49afb83883c26188e40af990ff306c5a1b60ab90fd0275/merged
shm              64M     0   64M   0% /data/containers/cf0dc03a4dfdd2107c49afb83883c26188e40af990ff306c5a1b60ab90fd0275/shm
overlay          15G  2.0G   13G  14% /data/overlay/79ab19aaa0b7cc14710d3cfe0390d403680e49fa25ed596d52330b36dd865a50/merged
shm              64M     0   64M   0% /data/containers/79ab19aaa0b7cc14710d3cfe0390d403680e49fa25ed596d52330b36dd865a50/shm
tmpfs           378M     0  378M   0% /run/user/0
```
I cant use apt-get clean or docker prune, do you have any other suggestions for clearing space on the VOXL? as the issue i get is ``` write /dev/stdout: no space left on device ```

Thanks in advance !

## Reply by Eric Katzfey (ModalAI staff) · 2021-07-07 15:32:30 UTC (in reply to kasarrowtec)

@Kasum-Hussain If you need the space just to build the docker image then you can use an SD card instead of /data.

## Reply by kasarrowtec · 2021-07-08 08:40:34 UTC (in reply to Eric Katzfey)

@Eric-Katzfey 

Hi Eric,

when using ```
docker save myimage:latest | gzip > myimage_latest.tar.gz```
how do i specify where to build the tar file ? to build on the SD card and not /data.

## Reply by Alex Kushleyev (ModalAI staff) · 2021-07-08 15:52:32 UTC

You can try `docker save myimage:latest | gzip > <path_to_sd_card>/myimage_latest.tar.gz` . <path_to_sd_card> should be `/mnt/sdcard`. 

Note that SD card will be quite a bit slower than built-in EMMC, you might want to do some testing to find a fast and reliable SD card.

From personal experience the following SD cards have worked well and fast:
- Lexar Professional 1066x
- Kingston 64GB microSDXC Canvas Go Plus

However there are plenty of SD cards to choose from, you may want to run some SD card tests before you use it for something important. There are some fake SD cards out there which result in corrupt data.

Also, if you wanted Docker to use SD card for storing all images, check this article : https://docs.modalai.com/docker-on-voxl/#move-docker-image-from-data-to-mntsdcard

## Reply by kasarrowtec · 2021-07-12 08:50:39 UTC

Hi Alex,

this was very helpful - got it working and managed to get the docker image out.

thank you for your help !