# Can't export data **URL:** \ **Category:** Support\ **Created:** [19 September 2023 17:44 UTC](https://community.vikunja.io/t/cant-export-data/1640 "2023-09-19T17:44:52Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Zweierpotenz](https://community.vikunja.io/letter_avatar_proxy/v4/letter/z/dec6dc/32.png) [@Zweierpotenz](https://community.vikunja.io/u/Zweierpotenz)\ **Post date:** [19 September 2023 17:44 UTC](https://community.vikunja.io/t/cant-export-data/1640/1 "2023-09-19T17:44:52Z")
First of all thanks for the great software. I just moved from Planka to Vikunja. I’m trying to export my data (inspired by this [post](https://community.vikunja.io/t/export-data-didint-work/562/7)) via CLI (I don’t have a mailer) but no file is written to the `files`-folder (docker-compose: `./files:/app/vikunja/files`). Log after boot: ```auto Recreating vikunja_db_1 ... done Recreating vikunja_frontend_1 ... done Recreating vikunja_api_1 ... done Attaching to vikunja_db_1, vikunja_frontend_1, vikunja_api_1 api_1 | info: creating the new user vikunja with 1000:1000 frontend_1 | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration frontend_1 | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ frontend_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh frontend_1 | 20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf frontend_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh frontend_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/50-injector.sh frontend_1 | info: API URL is /api/v1 frontend_1 | info: Sentry enabled: false frontend_1 | info: started at 2023-09-19T17:19:54+00:00 frontend_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/60-ipv6-disable.sh frontend_1 | /docker-entrypoint.sh: Configuration complete; ready for start up api_1 | usermod: no changes db_1 | 2023-09-19 17:19:54+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.5+maria~ubu2204 started. db_1 | 2023-09-19 17:19:54+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' db_1 | 2023-09-19 17:19:54+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.5+maria~ubu2204 started. db_1 | 2023-09-19 17:19:54+00:00 [Note] [Entrypoint]: MariaDB upgrade not required db_1 | 2023-09-19 17:19:54 0 [Note] Starting MariaDB 10.11.5-MariaDB-1:10.11.5+maria~ubu2204 source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1 db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Using transactional memory db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Number of transaction pools: 1 db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions db_1 | 2023-09-19 17:19:54 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Using liburing db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Completed initialization of buffer pool api_1 | 2023/09/19 17:19:54 No config file found, using default or config from environment variables. api_1 | 2023-09-19T17:19:54.887781515Z: CRITICAL ▶ migration/Migrate 002 Migration failed: dial tcp 192.168.48.3:3306: connect: connection refused db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: End of log at LSN=1497726 db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: 128 rollback segments are active. db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: log sequence number 1497726; transaction id 3025 db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool db_1 | 2023-09-19 17:19:54 0 [Note] Plugin 'FEEDBACK' is disabled. db_1 | 2023-09-19 17:19:54 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. db_1 | 2023-09-19 17:19:54 0 [Note] InnoDB: Buffer pool(s) load completed at 230919 17:19:54 db_1 | 2023-09-19 17:19:54 0 [Note] Server socket created on IP: '0.0.0.0'. db_1 | 2023-09-19 17:19:54 0 [Note] Server socket created on IP: '::'. db_1 | 2023-09-19 17:19:54 0 [Note] mariadbd: ready for connections. db_1 | Version: '10.11.5-MariaDB-1:10.11.5+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution api_1 | 2023/09/19 17:19:55 No config file found, using default or config from environment variables. api_1 | 2023-09-19T17:19:55.524686446Z: INFO ▶ migration/Migrate 052 Ran all migrations successfully. api_1 | 2023-09-19T17:19:55.524783421Z: INFO ▶ models/RegisterReminderCron 053 Mailer is disabled, not sending reminders per mail api_1 | 2023-09-19T17:19:55.524821445Z: INFO ▶ models/RegisterOverdueReminderCron 054 Mailer is disabled, not sending overdue per mail api_1 | 2023-09-19T17:19:55.524895494Z: INFO ▶ cmd/func25 055 Vikunja version v0.21.0 api_1 | ⇨ http server started on [::]:3456 ``` Then I do `docker exec vikunja_api_1 /app/vikunja/vikunja dump` and get the following in the CLI: ```auto 2023/09/19 17:21:58 No config file found, using default or config from environment variables. 2023-09-19T17:21:58.188215877Z: INFO ▶ migration/Migrate 052 Ran all migrations successfully. 2023-09-19T17:21:58.188310197Z: INFO ▶ models/RegisterReminderCron 053 Mailer is disabled, not sending reminders per mail 2023-09-19T17:21:58.1883445Z: INFO ▶ models/RegisterOverdueReminderCron 054 Mailer is disabled, not sending overdue per mail 2023-09-19T17:21:58.188498451Z: INFO ▶ dump/Dump 055 Start dumping config file... 2023-09-19T17:21:58.188520211Z: WARNING ▶ dump/Dump 056 No config file found, not including one in the dump. This usually happens when environment variables are used for configuration. 2023-09-19T17:21:58.188531952Z: INFO ▶ dump/Dump 057 Dumped config file 2023-09-19T17:21:58.188767225Z: INFO ▶ dump/Dump 060 Dumped .env file 2023-09-19T17:21:58.188782454Z: INFO ▶ dump/Dump 066 Start dumping version file... 2023-09-19T17:21:58.189365575Z: INFO ▶ dump/Dump 091 Dumped version 2023-09-19T17:21:58.189570124Z: INFO ▶ dump/Dump 094 Start dumping database... 2023-09-19T17:21:58.222848502Z: INFO ▶ dump/Dump 101 Dumped database 2023-09-19T17:21:58.222881939Z: INFO ▶ dump/Dump 102 Start dumping files... 2023-09-19T17:21:58.241135697Z: INFO ▶ dump/Dump 104 Dumped files 2023-09-19T17:21:58.241168724Z: INFO ▶ dump/Dump 105 Done creating dump 2023-09-19T17:21:58.241186231Z: INFO ▶ dump/Dump 106 Dump file saved at vikunja-dump_2023-09-19_17-05-58.zip ``` But the db logs the following ```auto 2023-09-19 17:21:58 4 [Warning] Aborted connection 4 to db: 'vikunja' user: 'vikunja' host: '192.168.48.5' (Got an error reading communication packets) ``` ---
**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\ **Post date:** [27 September 2023 08:34 UTC](https://community.vikunja.io/t/cant-export-data/1640/2 "2023-09-27T08:34:20Z")
`vikunja dump` does not write anything into the `files` directory. It uses the current working directory from where you run the command. ---
**Author:** ![Zweierpotenz](https://community.vikunja.io/letter_avatar_proxy/v4/letter/z/dec6dc/32.png) [@Zweierpotenz](https://community.vikunja.io/u/Zweierpotenz)\ **Post date:** [3 October 2023 10:58 UTC](https://community.vikunja.io/t/cant-export-data/1640/3 "2023-10-03T10:58:23Z")
Nothing is written to the working directory from where I run the command. The user own the directory and has write permissions. In [another thread](https://community.vikunja.io/t/export-data-didint-work/562/7) you said: > The data export file is put in the `files` directory you configured. Was this just meant for the backup started by the frontend? ---
**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\ **Post date:** [3 October 2023 11:25 UTC](https://community.vikunja.io/t/cant-export-data/1640/4 "2023-10-03T11:25:06Z")
> [@Zweierpotenz](#): > > In [another thread](https://community.vikunja.io/t/export-data-didint-work/562/7) you said: That’s about the User Data export, not the one from `vikunja dump`. ---
**Author:** ![Zweierpotenz](https://community.vikunja.io/letter_avatar_proxy/v4/letter/z/dec6dc/32.png) [@Zweierpotenz](https://community.vikunja.io/u/Zweierpotenz)\ **Post date:** [24 November 2023 20:53 UTC](https://community.vikunja.io/t/cant-export-data/1640/5 "2023-11-24T20:53:23Z")
Thanks for the clarification. But my problem that nothing is written to the working directory still persists. Any ideas why this might be. ---
**Author:** ![Mario](https://community.vikunja.io/user_avatar/community.vikunja.io/mario/32/956_2.png) [@Mario](https://community.vikunja.io/u/Mario)\ **Post date:** [25 November 2023 09:02 UTC](https://community.vikunja.io/t/cant-export-data/1640/6 "2023-11-25T09:02:00Z")
You’re running the command inside the docker environment, so the files are dumped inside the docker container in the default working directory. If you run `docker exec vikunja_api_1 sh` you’ll get a shell inside the docker image. Are the dumped files in **that** working directory? If so, you might want to mount a host directory, change to that, and then run the dump command. ---
**Author:** ![Zweierpotenz](https://community.vikunja.io/letter_avatar_proxy/v4/letter/z/dec6dc/32.png) [@Zweierpotenz](https://community.vikunja.io/u/Zweierpotenz)\ **Post date:** [25 November 2023 14:03 UTC](https://community.vikunja.io/t/cant-export-data/1640/7 "2023-11-25T14:03:02Z")
I already tried entering the API-container but made the mistake of trying to execute `bash` which is not available in it; so I gave up on it. But of course the working directory of the container was meant. I had to use `docker exec -it vikunja_api_1 sh` with `-it` so you can interact with it. So thank you @Mario and @kolaente for the help ---
**Author:** ![Zweierpotenz](https://community.vikunja.io/letter_avatar_proxy/v4/letter/z/dec6dc/32.png) [@Zweierpotenz](https://community.vikunja.io/u/Zweierpotenz)\ **Post date:** [25 November 2023 14:20 UTC](https://community.vikunja.io/t/cant-export-data/1640/8 "2023-11-25T14:20:31Z")
> [@Mario](#): > > If so, you might want to mount a host directory, change to that, and then run the dump command. Instead I used `docker cp vikunja_api_1:/app/vikunja/vikunja-dump_2023-11-25_14-02-45.zip ./dump/` to get the file to my host machine.