# Failed to unmarshal Stringorslice **URL:** \ **Category:** Drone Support\ **Created:** [February 26, 2018, 4:55pm UTC](https://drone.discourse.group/t/failed-to-unmarshal-stringorslice/9245 "2018-02-26T16:55:18Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jegger](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/jegger/32/3736_2.png) [@jegger](https://drone.discourse.group/u/jegger)\ **Post date:** [February 26, 2018, 4:55pm UTC](https://drone.discourse.group/t/failed-to-unmarshal-stringorslice/9245/1 "2018-02-26T16:55:18Z")
I installed drone on a fresh digital-ocean dropplet (2GB, debian 9.3) by installing docker (17.12.0-ce) and docker-compose first. After that I created the docker-compose.yml file with the content of: [http://docs.drone.io/installation/](http://docs.drone.io/installation/). I changed the secret, github-key and github-client variables and started it with docker-compose up. I am able to select the repository of my choice. In this case a fork of your python-demo: [https://github.com/jegger/drone-with-python](https://github.com/jegger/drone-with-python). After pushing a dummy commit, drone “starts” the build. But it fails with the error “ **Failed to unmarshal Stringorslice** ”. Sadly I am not able to see any helpful messages in the logs. My guess indicates that this error comes from parsing some yml file… Can you guide me on how I can debug this further? Did I do something obviously wrong? (I tried it with bitbucket-cloud, older / newer versions of drone, drone via rancher-catalog, different project with simpler .drone.yml file…) Thanks, ---
**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\ **Post date:** [February 26, 2018, 5:09pm UTC](https://drone.discourse.group/t/failed-to-unmarshal-stringorslice/9245/2 "2018-02-26T17:09:00Z")
This error would indicate your Yaml file is malformed and cannot be parsed. Please provide a copy of your Yaml and I can advise further. ---
**Author:** ![jegger](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/jegger/32/3736_2.png) [@jegger](https://drone.discourse.group/u/jegger)\ **Post date:** [February 26, 2018, 5:12pm UTC](https://drone.discourse.group/t/failed-to-unmarshal-stringorslice/9245/3 "2018-02-26T17:12:01Z")
Thanks for your quick answer. Are you talking about the .drone.yml file? As I am using the drone-with-python repo-fork: [https://github.com/jegger/drone-with-python/blob/master/.drone.yml](https://github.com/jegger/drone-with-python/blob/master/.drone.yml) I also tested it with my drone-test repo: [https://github.com/jegger/dronetest/blob/master/.drone.yml](https://github.com/jegger/dronetest/blob/master/.drone.yml) =\> Both have the same error. ---
**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\ **Post date:** [February 26, 2018, 5:14pm UTC](https://drone.discourse.group/t/failed-to-unmarshal-stringorslice/9245/4 "2018-02-26T17:14:36Z")
The yaml file at this link is invalid: [https://github.com/jegger/drone-with-python/blob/master/.drone.yml](https://github.com/jegger/drone-with-python/blob/master/.drone.yml) It appears to use an outdated version of the .drone.yml format which was deprecated a few years ago. You will need to update the Yaml to use the latest format, as described here: [http://docs.drone.io/pipelines/](http://docs.drone.io/pipelines/) ---
**Author:** ![jegger](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/jegger/32/3736_2.png) [@jegger](https://drone.discourse.group/u/jegger)\ **Post date:** [February 26, 2018, 5:25pm UTC](https://drone.discourse.group/t/failed-to-unmarshal-stringorslice/9245/5 "2018-02-26T17:25:07Z")
Thanks! I knew it had to be something obvious. I was to focused on this drone-with-python demo to see that the syntax in the doc had changed. Thanks again